Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Add a new field with the button .
  • Change the order of the fields in the workflow form, just drag and drop with holding this icon .
  • Remove a field with the icon , the icon is displayed at the right when you select the row of the field.
  • You could update the Label of the field displayed in the workflow.
  • Also you could update the Name of the field.
  • By default, the fields are in write mode, if you want display the field in read only mode, please mark the checkbox .
  • You could add a custom script to validate the value of the field.
  • You could add a custom script to decide the conditions to display the value.

In a validation or a visibility script you could access to the fields as the next script.

Code Block
if (object{"userName"}==null){
	throw new Exception("The userName is mandatory");
}
return true;


Triggers

In this tab you could create custom scripts to be triggered from some actions.

...

  • OnLoad. To perform some actions before the execution of the step.
  • OnPrepareTransition. To perform some actions after the execution of the step and before to start a transition to another step.
  • OnChange. When the value of the attribute if changed. You could choose the filed from a list.

In a trigger script you could access to the fileds as the next script:

Code Block
// Example 1
executionContext.setVariable("profileServer", "null");
executionContext.setVariable("homeServer", "null");
executionContext.setVariable("mailServer", "null");
executionContext.setVariable("userType","A");
un = executionContext.getVariable("userName");
executionContext.setVariable("userName", un+"_INT");

// Example 2
a = executionContext.getVariable("shortName");
u = serviceLocator.getUserService().findUserByUserName(user);
s = serviceLocator.getDispatcherService().findDispatcherByName("OC_DTVEXT");
u.userName = an+"_ATT";
account = serviceLocator.getAccountService().createAccount (u, s, a);
serviceLocator.getUserService().update(u);
serviceLocator.getAccountService().updateAccount2(account);


Incoming transitions

In this tab you could see the previous steps those it has connected.

...

These attributes will be used in the Steps tab to be mapped with the Soffid data.

About the generated workflow

Once you have a workflow named User.

Image Added

With this configuration.

Image Added

After publish it, the final user with the correct permissions will find the workflow here.

Image Added

When you enter into the workflow the first page is the form generated from the fields and configuration of the step Start.

Image Added

The header of the page is common for all the workflows.

Image Added

In the body of the tab Task, all the fields of the step Start are displayed.

Image Added

And the button Image Added is the Outgoing Transition of the step Start to go to the Approve step.

Now the identities configured in the step Approve as managers should accept or remove this user creation request.

The manager will receive a mail and they could access to the workflow in My tasks page.

Image Added

Notice that the workflow complete the Start step a workflow

...

Pendingidentifier is created to be found and observed for the creation user, manager and observers.

Image Added

Once the manager is into the workflow he could read or update the fields configured in the step Approve.

Image Added

At this moment the manager has to get the task with the button Image Added and update the editable fields.

Image Added


And finally decide if Image Added or Image Added the user creation.

Resources

Below you could find a set of workflows that you could import, edit and publish in your Soffid instance:

...