Events
There is a new tab called âEventsâ for every block in the GUI where events can be configured. The events allow Policy creators to transfer control/execution on exit from the current block to an arbitrary block and thus build non-linear workflows.
Settings:
Note: The event is shown in both source and target blocks tabs regardless of where it was added initially.
Default Events
Default events correspond to the implicit default transfer of execution control from the current to the next (adjacent) block graphically represented by the block immediately below the current one.
Default events can be switched off by setting âDisabledâ to âtrueâ on the Events tab, or âStop Propagationâ to âtrueâ on the Properties tab as in the older Guardian versions.
Output Events
Output events are events which are created by the âSourceâ blocks.
Output Event (enum):
All Blocks:
RunEvent - appears upon the completion of main logic of the block.
RefreshEvent - triggered upon the changes in the state of the block.
TimerBlock:
TimerEvent â triggered upon each âtickâ of the timer
switchBlock:
Condition 1..N - each condition expression in the switch block maps to the corresponding event created upon the evaluation of its condition into âtrueâ
InterfaceActionBlock:
Option 1..N - each Option (button) triggers a corresponding event upon the button press action from the user
Calculate Block, Custom Logic Block, DocumentValidatorBlock, ExternalDataBlock, MintBlock, Reassigning Block, RequestVcDocumentBlock, RetirementBlock, RevokeBlock, SendToGuardianBlock, TokenActionBlock, TokenConfirmationBlock
Error Event : Which is called and passed the input data when error occur.
Input Events
Input Events are received and processed by the egress interface of the âTargetâ block.
Input Event (enum):
All Blocks:
RunEvent - triggers the execution of the main logic of the block.
RefreshEvent - triggers the refresh of the block (in the UI it re-draws the component)
aggregateDocumentBlock:
TimerEvent - triggers the execution of the time(period)-activated aggregation logic, and passes the aggregated data further
PopEvent - removes the document from the aggregation.
timerBlock:
StartTimerEvent - starts the timer for the user (to âtickâ for the time-activated aggregation logic)
StopTimerEvent â stops the âtickingâ timer for the user
RequestVcDocumentBlock:
RestoreEvent - Which receive input vc document to restore data.
mintDocumentBlock:
AdditionalMintEvent - allows linking of the result of one mint block with another mint block.
RetryMintEvent - It allows to retry mint action if there were some errors, issues there. Environment variable RETRY_MINT_INTERVAL is setting up retry mint interval (in minutes), default is 10 minutes.
Note:
The link starts with âRunEventâ of the main Mint Block and ends with âAdditionalMintEventâ of the secondary Mint Block
âDefault Eventâ of the main Mint Block must be switched off if linked Mint Blocks follow each other
Event Actor
Allows to change the user-context of the execution
For example: in the situation where the Standard Registry confirms the form data from the user and the Policy author would like to come back to the execution of the StepBlock as the original user the âDocument Ownerâ should be configured here instead of the âEvent Initiatorâ.
Event Initiator - Actor which triggered the event.
Document Owner- Actor is changed to the owner of the document.
Document Issuer - Actor is changed to the user who signed (confirmed) the document.
Viewer
Output events
Input events
Default Events
Tooltips
Filters
Last updated