https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/notice_design/index.html Recent content in 4.3.3 Designing notifications on JP1 Cloud Service/Operations Integration User's Guide Hugo -- gohugo.io en https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/notice_design/notice_ex/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/notice_design/notice_ex/index.html The following are use cases of notification conditions triggered based on schedule and work items. Clicking each use case number will take you to the description of the use case. (Table) Examples of notification conditions based on schedule and work items Use cases Trigger Notification condition 1 Work item Notifies of work item creation and updates. However, if only the display order of work items is changed, no notification is made. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/notice_design/notice_workflow_ex/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/notice_design/notice_workflow_ex/index.html This section shows an example of how to define notifications to be sent at any point in the workflow. When the notification "type" is set to "onDemand", notifications can be sent at any timing specified in the workflow. You can embed values from workflow fields or parameters configured in the Workflow YAML file into the notification content as follows: Use .GetValue For a list of available values, see "(Table) Object fields that can be used in Notification".