Are you familiar with this: quickly changing a document to the next state in the context menu — oops, it should have been the doument one row underneath! “Oh well, I can just change the state again so that it’s right”. However, if in-STEP BLUE is configured so that colleagues are automatically informed of state changes via email and the new state change has to be carried out by someone with another role, it’s not quite so simple. So much effort because of one wrong click.
Now you can secure the state transfer with a password request. This helps avoid errors and to increase security. Especially recommendable is the implementation of a new feature for state tranfers, that should document, in combination with reviews and acceptances, the confirmation or rejection of the examiner.
More security in two minutes
Let’s assume you want use password entry to secure the state change of a ticket form that documents the completion of the ticket editing. How do you do it? Configure the command server … for products. Open the component management in the menu row under organizational unit and then under Components. Navigate to the command server and configure the events (in our example the event abschleißen/close) for which a password should be requested.
That was already the whole configuration. Now, every time the action close is triggered, the password of the current user will be requested.
And now you will already be asked for your password.
Do you have requestions or remarks about this feature? Get in touch at firstname.lastname@example.org or 030/467086-20. We are looking forward to hearing from you.