Follow my blog...........

var gr = new GlideRecord('sn_sm_finance_request'); var num = current.sys_id; if (gr.get('sys_id',num)) {         var variables = gr.variables.getElements();     for (var i=0;i<variables.length;i++) {         var question = variables[i].getQuestion();         if(i==0 && question != ""){             var Opco = question.getValue();             var gr = new GlideRecord('core_company');             gr.get('sys_id',Opco);              var display = gr.getDisplayValue();             task.u_operating_company = display;         }         if(i==2 && question != ""){ ...

The  Flow Designer support for the Service Catalog  plugin (com.glideapp.servicecatalog.flow_designer) adds the Service Catalog trigger to Flow Designer. The Flow Designer support for the Service Catalog does not require a separate subscription. To activate the plugin on your company instance, request activation through the HI Customer Service instance.

Notifications send outbound email to one or more recipients in response to specific activities in ServiceNow. Notifications can be sent when: Records are inserted or updated Events are generated The Notification activity executes in a workflow  Administrators can use the Application Navigator in the main ServiceNow browser window to open  User Administration > Users  to see a list of user records. Email : User's email address Calendar integration : Set to either --None-- or Outlook. When set to Outlook, users can receive calendar appointment notifications. DEVELOPER TIP : To force a notification to be sent even if recipients have unsubscribed, developers can modify the Notification form layout to include the Force delivery field. When selected, notifications are sent regardless of user notification preference settings. DEVELOPER TIP : ServiceNow sends notifications to all recipients in the Who will receive section even if those users are not authorize...

Workflows can have three states: Checked out : executes only for the user who has the workflow checked out Published : executes for all users and records meeting the workflow conditions Unpublished : no longer available for new contexts but may still be running for older contexts Only one published version of a workflow exists in runtime for new contexts. When a workflow is invoked, the current workflow definition is loaded into the workflow context.

Checking Out a Workflow To prevent developers from making changes to a workflow that will impact other users, workflows need to be checked out before they can be edited. When a workflow is checked out, changes are applied to the workflow only for the user who checked it out. When development is complete, workflows must be published to be active in the environment. Every workflow activity has a different set of configuration fields. The configuration fields are dependent upon what an activity does. For example, the Approval - User activity needs to know the approver(s). Validating Workflows Workflow validation is the first step to ensure a workflow is error-free. Validation cannot test whether a workflow works as expected. Validation prevents workflows with critical flaws from executing and resulting in an unstable or incomplete state. Validation checks for issues like: Activities with missing transitions Multiple or missing End activity Invalid table references ...