This process has an instantiation (initial) Generic Request Form to be completed by a User. When the User logs in to make a request, the Process takes the User’s information (first name, last name, and email address) from the User Profile in UserXP.
At the Step "Approve or Reject," the manager of the requestor is approves or rejects the User’s request. On completion, an email Connector sends a message to the requestor.
You can use the provided test Users John, Jack, and James.
Here is a delegation management process :
If you go on holidays , just delegate all your tasks to a specific user.
What it does is checking periodically ( you can chose the frequency ) if there are tasks assigned to you and , if there are , it adds your delegate to the candidates .
I have already included a notification e-mail that lists the tasks assigned , you just need to setup it :)
I am sure that all of us, either in daily life or at our organizations have some defined processes that are followed for how we do various activities. For example, when we want to ask for a new computer, we know that we need to go to the administrative office and request it from there and there could be forms to fill and signs to get. There could be a waiting period involved and there will be an inspection when the new computer arrives and finally when all is well the request is completed and closed.
From Bull Spain (www.bull.es) want to share the experience accumulated during these years develop using the workflow engine Bonita, so we will make available to the community some of the connectors we have developed in the latest BOS versions. Expecting it result very useful !!!
This connector adds a list of users and their memberships (groups and roles) on Bonita database using IdentityAPI. Non-existant users/groups/roles are created. Tested with BOS 5.7.2. How to use it: see comments below.
This connector takes as input the description of a payment transaction, and returns an URL at PayPal to process this transaction.
It uses the basic PayPal Forms Web API (https://www.x.com/docs/DOC-1332), and does not have a dependency.
Here is a quite useful process !
This process will allow you to manage your other processes rights and the global policy !
With it , you will be able to define which users or which groups are able to start or read defined processes .
You will also be able to chose whether all your user can start processes by default or none of them can .
There may be some french bits remaining in the code / strings , please tell me so i can remove it.
You need to add a process variable (text type) where this join checker will store a value if the veto rule matches.
You need to add a step variable (text type) where you will store the answers (votes) of your users.