Platform Generate my work plan agentic workflow

Use the Platform Generate my work plan agentic workflow to create personalized work plans for currently assigned work.

Generate my work plan overview

The Generate my work plan agentic workflow creates personalized work plans based on current assigned work. This reduces manual effort and guesswork in work planning. The AI agents identify and retrieve all work assigned to the user, predict effort required to complete work, and generate an actionable work plan. Effort is estimated based on historical records related to the open work items. Generated work plans emphasize the highest priority work by examining the following information and can result in faster resolution and fewer missed SLAs.

• User sentiment
• Short description
• Priority
• Description
• Due date
• Escalation
• State
• Updated
• Number
• Impact
• SLA

Along with the plan itself, the agentic workflow also provides reasoning behind its decisions for creating the plan.

The agents, tools, and triggers associated with the Generate my work plan agentic workflow are provided by Now Assist applications. You can activate the agentic workflow template by adding triggers and setting the display settings to include the Now Assist panel. To change this agentic workflow's instructions, duplicate it, adjust the settings to suit your specific needs, and activate the duplicated version instead.

Prerequisites and setup

To access this workflow, you must have Now Assist for Platform installed on your instance. You can get this by installing any other Now Assist application, such as Now Assist for IT Service Management (ITSM).

Now LLM is not a supported LLM provider for the Generate my work plan agentic workflow.

Role masking

Required role: sn_uxc_gen_ai.platform_ai_work_planner.

Role masking enables users to limit the roles and privileges of agentic workflows during tool execution. Agentic workflows and their AI agents that get installed with Now Assist applications are assigned pre-defined roles. If you select Users with specific roles for user access, you must configure the security controls to include these roles. Data access settings must also include these roles. For the instructions to change the security controls, see Define security controls for an agentic workflow.

In the data access settings, add the necessary roles to enable reading of the tables for the records you want to access for potential work plans. For example, add the itil role to the agentic workflow's list of approved roles so that it can access Incident records.

Additional configuration

Change different settings related to the agentic workflow by changing values for the Now Assist Skill Config Var Set. To access the variable set and make changes, do the following while in the Platform AI Agents and Skills scope:

• Go to the Now Assist Skill Config [sn_nowassist_skill_config] table.
• Open the record named Generate my work plan config.
• In the Now Assist Skill Config Var Set related list, select New.
• Enter a name for your Config Var Set.
• Set Config Type to be either User schedule or Generate my work plan.
• Save the Var Set record.
• Set the variables for the config type.
• Save the Var Set.

The work plan config var set includes general variables for running the agentic workflow.

Table 1. Work plan config type configurations

Config field	Description
Schedule job	Creates a scheduled job that automatically runs, allowing users to see updated prioritization suggestions after making progress in their work. Default: Unselected.
Schedule job frequency	How long after a record in the original work plan is updated for the agentic workflow to run again. Default: 30 minutes
Predict estimates	Predict estimated time to complete work per record.
Exclude task table	By default, certain fields are used for prioritizing work on the Task table. You can configure what fields to use on individual tables, such as the Incident table. Enable this to only plan for tables configured and not other records which are task or extension of task tables.
Max tasks	The maximum number of tasks that can be recommended to a user for their work plan. Default: 30 tasks

The Incident config var set includes the following variables. Configure either the AIS fields or the GAF field for determining how the agentic workflow gathers what work the user has. If you configure GAF, it takes priority when running the agentic workflow. For more information about GAF, see Group Action Framework.

Use this config var set as a template to change any values for other tables, such as the Case or HR Case tables.

Note:

If you select Exclude task table in the work plan config var set, only the tables that have these var sets configured are included for work in the suggested work plan.

Table 2. Incident table config type configuration

Config field	Description
Table	Table for record types that someone can work on
Conditions	Filter criteria for determining eligible tasks
Record fields	Fields passed to the workflow for analysis
Time worked	Custom or edited field for specifying time worked. By default, the agentic workflow uses the Time worked field.
AIS Search Profile	Specific AI Search profile
AIS Search Fields	Fields AI Search looks at for determining similarity
AIS Return Fields	Fields returned by AI Search to the agentic workflow to base decisions on
GAF Config	Group Action Framework grouping configuration record, which is a collection of groups of records to make searching easier.
Assigned to field	The field for the user who works on the record. By default, the agentic workflow uses the assigned_to field.
Order by	JSON object array containing the ordering information for how work records are prioritized. Default is as follows. Any direction other than “DESC” is considered ascending in order. [ { column: 'priority', direction: ''}, { column: 'due_date', direction: ''}, { column: 'escalation', direction: 'DESC' }, { column: 'sys_created', direction: 'DESC' } ]

By default, the Generate my work plan agentic workflow relies on the User [sys_user] record's Schedule field. If there is no schedule defined on the User record, the workflow consults the Schedule [chm_schedule] table for the user. If neither are present, the assumed schedule is a weekday schedule from 8:00 a.m. to 5:00 p.m.

Change what tables and fields to look for schedule information with the User schedule config type.

Table 3. Generate my work plan User schedule configuration

Config field	Description
Table	Table where user schedule information is stored
Conditions	(Optional) Conditions to determine what user schedule to associate with the user.
Schedule column	Field where specific schedule information is stored

Accessing the Generate my work plan agentic workflow

To access the agentic workflow:

1. Navigate to All > AI Agent Studio > Create and manage.
2. Select Generate my work plan.

The first step of the guided setup includes a complete list of included AI agents. Selecting the name of an AI agent opens it in AI Agent Studio, where you can see the full description, role, list of steps, and tools. Tools are displayed in the second step of the AI agent guided setup, Add tools and information.

In-product agentic AI and UI actions

Access agentic workflows in the Core UI and in workspaces in the AI Activity panel. From there, track their progress, provide or review input, and see the results of the work performed. For more information, see In-product agentic AI for more details about the AI Activity panel.

To enable users to access agentic workflows with UI actions, open the agentic workflow in AI Agent Studio and navigate to the Select channels and access step. Select a UI action as a possible way to access the workflow.

If you don't see your UI actions after configuring it in AI Agent Studio, verify that the property com.glide.agentic_processes_view.enabled is set to true. See Enable the in-product experience for agentic workflows.

Testing the Generate my work plan agentic workflow

Manually test an agentic workflow execution or access on the Testing page of AI Agent Studio if you have the sn.aia_admin role and all other roles configured in the security controls. Start a manual test, select a test type and the name of the workflow, and use utterances in the Task field like the following samples. See Test an agentic workflow execution.

To evaluate the agentic workflow over many different execution logs, run an automated evaluation.

Sample utterance

After the workflow is activated in AI Agent Studio, enter What should I work on today? or similar phrases in the Now Assist panel to trigger the workflow. You must have the sn.now_assist_panel_user role to run the workflow. Also run this workflow on the Testing page of AI Agent Studio with the same utterance in the Task field if you have the sn.aia_admin role.

Users must have the sn_uxc_gen_ai.platform_ai_work_planner role to execute the agentic workflow.

AI agents used in the Generate my work plan agentic workflow

The following table lists the agents used in the Generate my work plan agentic workflow.

Important:

In the Select channels and status step of each AI agent's guided setup, verify that the Status toggle is enabled to activate the AI agent.

Table 4. AI agents names and descriptions in the Generate my work plan agentic workflow

AI agent name	AI agent description	Role required
Prioritize work AI Agent​	Dynamically orders tasks based on parameters like urgency, priority, SLAs, sentiment, and impact.	sn_uxc_gen_ai.platform_ai_work_planner

Other Platform agentic workflows

For more information on other agentic workflows associated with the Platform workflow, see Platform agentic workflows.