IdStory Identity Manager

Create two new entities: SysProvisioningBreakConfig and SysProvisioningBreakRecipient for both entities was created service layer, controllers, filters, dtos. Permission for create update break configuration is SYSTEM.

Start with FE - create table with configs and detail.

Implemented new processor: Provisioning Break Processor, in this processor is all logic break provisioning operation. Provisioning operation isn't counted from archive or batch, but from cache. Cache is placed into SysProvisioningBreakConfigService.

Yesterday i was updated entity SysProvisioningBreakRecipient and SysProvisioningBreakConfig with indexes and rename some columns.
Also finished localization FE and complete FE + error message, add toPredicates methods for both services.

I started with testing provisioning break

Feedback from consultation from ZB and team:

• notification with warning send only once, after exceeding the limit.
• global provisioning break create separately for each provisioning operation (create, update, delete).
• user or role in provisioning recipient may be code, username and etc.,
• remove attribute blockOperation in provisioning break config,

For component TextField update method getRequiredValidationSchema, for joi definition: number, allow(0), unsigned and required isn't possible validate number correectly - i fixed this problem.
Add data integrity check between role, identity and provisioning break recipients.
Resolve conflict with new system processors.
Template for disable and warnign system are done.
Start with tests and documentation

Create test for provisioning break. Missing only documentation.

Documentation: https://wiki.czechidm.com/devel/dev/provisioning/break

Im so sorry for not added commits with code, but there is so many commits :( main logic is in processor, so please check processor for provisioning break, thank you.

Tutorial: https://wiki.czechidm.com/tutorial/dev/create_provisioning_break

Please Radek could you make a review? Thank you very much, if you have any problem with code, please tell me i explain it or fixed. Thank you.

I fixed problem with empty list in provisioning break agenda.
commit: https://github.com/bcvsolutions/CzechIdMng/commit/4038393a0d79ce7a6ef150e36bd2bb2f9cf0a5ea

New agenda works and looks nice, code is nice too. I found some issues:
- Exceptions have to be handled in processor and ProvisioningException has to be thrown out - when some exception occurs, we need to know in provisioning operation agenda and its based on ProvisioningException (rollback is called otherwise).
- when (global) configuration limit is set to 1, then null pointer is thrown from sendMessage method
- notification should have level warning and error
- send warning and disable operation has to be done after given limit is exceeded (not is warning send, when given limit is processed)
- result codes are not localized on FE

I've changed some FE contents (css, columns, messages).

Thanks Radek for feedback.

• wrap all logic in provisioning break into try and catch,
• now is send warning and disable system when limit is exceeded (also fix tests),
• rename EN localization to brake,
• topics are now both warning,
• localized result codes from errors on FE.

Add two new test for 0 limits. Thanks for feedback and directly fix FE issues.

Thx!