- Publication date
- Reading time
The summer temperatures have made us sweat, now autumn has cooled us down! We think this is the perfect time to share four hot tips with you process designers to make you feel warm again! We asked our consultants how they could approach their digitization projects even more efficiently. The result is now available in our blog: Check out our daily hacks for process design with JobRouter®!
1. Thinking ahead rather than re-thinking: the right start counts
Clarify at an early stage who will assume the role of the process owner and who can bring the right input from the specialist department. This role is particularly important after the go live of the workflow in order to be able to respond to requests from users for individual workflows and control the current instances.
Create a rough concept together with the process managers and stakeholders and design dialog interfaces in this phase in order to build understanding for the planned solution among all participants. Define the necessary interfaces and those responsible at this point.
2. Use process messages for process creation
Process messages are a proven means of storing and maintaining JobRouter® process names and texts in a central repository. Through the consistent use of this repository, you save a lot of time during the development of the processes, since you only have to select a name once it has been entered. However, it is particularly interesting to make changes to processes and forms, since descriptions can run through many dialogs and are therefore prone to errors. This is where process messages play their greatest trump card. They also offer advantages in a possible translation of the workflow. Simply export all descriptions as Excel files and pass them on for translation. Done.
3. Less is more: not every requirement must be modelled in the process
Every process designer knows this scenario. When a new process is started or implemented, more and more requirements are placed on you as the designer. In particular, the various special cases can present a great challenge and increase the complexity of the process.
Check carefully whether this investment is worthwhile. Especially with regard to testability. For the first version of the workflow, use standard functionalities such as queries or assignments to map special cases. Analyze later which special cases occur frequently and are worth adapting the process to them.
4. Involve all those responsible in the process
As a process designer, your goal must be to be as free as possible for new processes or change requests after the implementation of a workflow. Therefore, free yourself from tasks such as data maintenance. JobData offers you the possibility to store lists and master data centrally and to enable certain users to edit them via profiles. Use this component so that process owners can manage this data independently. Business rules such as release limits can also be defined centrally in this way.