This document describes how to create a one-step from scratch.
One-Steps are groups of actions that can be run in WiscIT in order to simplify a repetitive or complicated actions. Commonly, they are added to a toolbar for ease of use in normal workflow processes. Pre-existing one-steps exist and can be added to a toolbar following these steps: [Link for document 48722 is unavailable at this time.]
This document outlines the creation of new one-steps with no background knowledge
One-Steps are powerful tools. Some examples of what One-Steps can do are send emails (automatically, or by opening a template that can be edited before sending), assign incidents to different teams or individuals, update repetitive information on business objects, and much, much, more.
We suggest that before you attempt to create a One-Step, that you lay out a clear plan of what you want it to do in the end. If it seems complicated, or beyond the scope of what is covered in this guide, feel free to send the WiscIT Team an email at email@example.com and an administrator would be more than happy to assist you.
A business object is something like an incident or change request that contains stored information. A majority of one-steps modify a business object's fields, such as which team or team member it is owned by, or the needs attention flag. Let's create a one-step and take a look at how this can be done.
NOTE: You can click the little pencil icon to see which fields you have edited for the given search criteria.
Logic can be used within a one-step to make decisions based on field values, stored values, variables, and user information. Some examples of when logic are used are:
Logical expressions are able to return either true or false back to the one-step. Whether it is true or false depends on which condition that is configured. For case 1 we will configure it to see if the variable we set earlier equals "yes". If so, the one-step will proceed down this branch. If not, then the one-step will check the next case until it reaches default.
Fields of a current object can also be used in order to make logical decisions. Instead of prompting the user for input, instead the expressions in the "Decide Between Multiple Cases" can use fields without needing variables at all.
Double Clicking on a step will bring up action conditions, which are conditions that must be met in order for the step to be run. If the conditions are not met, the step is skipped and will go on to the next step.
Emails and Text-Modifiers are important parts of processing text in an incident. This step will detail how to display information, as well as how to easily use this formatting to send emails to customers
WiscIT can spoof any email address that you enter into the "From:" field. A common strategy is to right click the "From" field, press the + button to the left of System Functions, and select CurrentUserEmail(). Then, emails sent will appear as being from you.