https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/ Recent content in Configuration on Syniti Documentation Hugo -- gohugo.io en-us https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Assign_a_Backup_User/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Assign_a_Backup_User/ Assign a Backup User There may be occasions when a user is unavailable for a period of time and there may be a need for a backup user to perform their tasks during their absence. A Security Administrator has the ability to assign a backup user with a start and end date to a primary user, and a user can assign a back-up user to their account. Upon assignment, the backup user retains their original security rights, acquires all security rights given to the primary user and then can perform the tasks of the primary user. https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Configure_a_Registered_User_to_Receive_Notifications_For_Posting_Success_or_Failure_at_the_Request_Role_Level/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Configure_a_Registered_User_to_Receive_Notifications_For_Posting_Success_or_Failure_at_the_Request_Role_Level/ Configure a Registered User to Receive Notifications For Posting Success or Failure at the Request Role Level A Designer can configure settings at the request role level for the Post role that determine if users registered in the platform receive a notification when a request posts successfully or fails to post. To add a registered DSP user to the Request Post Workflow Notification page, select the User ID from the USER ID field then save the record. https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Configure_SLA_Settings_at_the_BPSR_Level/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Configure_SLA_Settings_at_the_BPSR_Level/ Configure SLA settings at the Business Process Scenario Role Level A Designer can configure SLA settings at the Business Process Scenario Role level. The SLA settings are inherited from the settings at the scenario > role level, but can be configured for the business process scenario > role combination. Refer to Setting up SLA notifications in dspConduct™ for more information about the prerequisites for setting up SLAs and how the SLAs work at the various levels for dspConduct™ elements. https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Configure_Workflow_Messages_Overview/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Configure_Workflow_Messages_Overview/ Configure Workflow Messages Overview Requests are workflow-enabled, meaning that each user assigned to a role in a request receives a notification when the tasks assigned to that role have work assigned. For example, when a user finishes a role by clicking Finish on the Request Rolepage, the Finish event is triggered, and an email notification and/or a pop-up notification from within dspConduct™ is sent to the next person(s) responsible for subsequent role(s). https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Create_Language-specific_Workflow_Messages_for_a_Category/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Create_Language-specific_Workflow_Messages_for_a_Category/ Create Language-specific Workflow Messages for a Category dspConduct™ sends Workflow messages to users as a request moves through the workflow. By default, these messages are in English. If the notification text must use a language other than English, a Designer should create Category Workflow Language Messages for each relevant language that is marked Active in DSP®, though this is not required.. NOTE: Regardless of the notification’s language, a Designer must navigate to the Category Workflow Language Message page for workflow messages to be created. https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Edit_Category_Language_specific_Messages/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Edit_Category_Language_specific_Messages/ Edit Category Language-specific Messages By default, dspConduct™ sends workflow messages to users who have access to a request when a request is created, canceled, deleted, finished, rejected or reset. dspConduct™ is installed with default workflow messages in English and the processing to send these messages. Default messages are used as the starting point for Category Language-specific messages. A Designer can modify the Subject, Message, and Email From to fit a specific language, or can update the Default message information for English language messages. https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Manage_Request_Statuses/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Manage_Request_Statuses/ Manage Request Statuses Overview The Request Statuspage lists the default statuses installed with dspConduct™. Default status cannot be edited or deleted. Default statuses have settings configured for archiving a request, editing a request, and allowing role access to the request. If the ARCHIVABLE check box on the Request Statuspage is enabled for a status, a request in the status can be archived. By default, a request is archived if it remains in the same status for 30 days. https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Send_Workflow_Notifications_when_a_Final_Finish_Package_Fails/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Send_Workflow_Notifications_when_a_Final_Finish_Package_Fails/ Send Workflow Notifications when a Final Finish Package Fails If a Final Finish package is created but does not run successfully, a user who belongs to the Final Finish Admin WebApp group receives a workflow notification. These users have read-only access to all requests across categories, and can ensure that the issue is investigated by the proper resources. A user can receive a workflow email, view the notification as a popup message from within dspConduct, or both. https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Send_Workflow_Notifications_when_a_Post_Fails_or_Succeeds/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Send_Workflow_Notifications_when_a_Post_Fails_or_Succeeds/ Send Workflow Notifications When a Post Fails or Succeeds Requests are workflow-enabled, meaning that each user assigned to a role in a request receives a notification when the tasks assigned to that role have work assigned. By default, dspConduct™ does not send notifications when a request has succeeded or failed to post (i.e., when the request’s posting status is Success or Failed). A Designer can configure settings at the scenario role level or the request role level for the Post role that determine if users registered in the platform or external users (users who are not registered and cannot log in to the product) receive a notification when a request posts successfully or fails to post. https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Set_Calendar_Used_For_Business_Value_Calculations/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Set_Calendar_Used_For_Business_Value_Calculations/ Set Calendar Used For Business Value Calculations An Administrator can set the calendar that is used to calculate the Request Working Hours for the business value dashboard calculation. The calendars are maintained in Common. Refer to Use a Calendar for more information. To set the calendar used for business value dashboard calculations: Select Configuration > Setup > Parameters in the Navigation pane. Click Edit. View the field descriptions on the Parameters page https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Set_Currency_Display_Label/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Set_Currency_Display_Label/ Set Currency Display Label An Administrator can set the currency label that is displayed on the Business Process page’s Vertical View for the currency associated with the Average Cost Per Hour value field. Updating the setting only changes the label. This setting does not accomplish any currency calculations or conversions. NOTE: This is the currency label for the Average Cost Per Hour value field for a business process if this label is changed the Average Cost Per Hour value may need to be changed as well. https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Set_Preceding_Weeks_Count_for_Dashboards/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Set_Preceding_Weeks_Count_for_Dashboards/ Set Preceding Weeks Count for Dashboards An Administrator can set the number of prior weeks to display on the count metrics charts. To set the Preceding Weeks Count for dashboards: Select Configuration > Setup >Parameters in the Navigation pane. Click Edit. View the field descriptions on the Parameters page. Enter the number of prior weeks to display on the count metrics charts in the Preceding Weeks Count field. https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Set_the_Days_Active_for_a_Request_Status/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Set_the_Days_Active_for_a_Request_Status/ Set the Days Active for a Request Status A Designer can configure how long the request data stays in the main request tables before it is archived. Before this task can be completed, Create a Category and Add a Custom Request Status. NOTE:Adding a custom request status is only necessary if a status other than the default statuses is needed To configure the category request status in dspConduct™: Select dspConduct **> Design** in the *Navigation* pane. https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Set_Up_Security_for_dspConduct/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Set_Up_Security_for_dspConduct/ Set Up Security for dspConduct™ To set up security: Create User Accounts in Common or have an Administrator create them in System Administration. NOTE; Adding a user in Common allows for a more streamlined process for password maintenance, and is the recommended method for use by a Help Desk or Call Center. In Common, password maintenance is the user’s responsibility. In System Administration, the Administrator must add a password for the user. https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Set_Up_Service_Pages_for_SLAs/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Set_Up_Service_Pages_for_SLAs/ Set Up Service Pages for SLAs The Request SLA Notification Service page determines which request roles are late to be processed. The Request SLA Notification Workflow and Request SLA Summary Workflowservice pages views the records created by Request SLA Notification Service page and sends the workflows necessary for those late request roles. An Administrator configures service pages. If the client site requires workflow notifications, the Request SLA Notification Service page and either the Request SLA Notification Workflow or Request SLA Summary Workflow Service pages must execute. https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Set_Up_SLA_Notifications/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Set_Up_SLA_Notifications/ Set Up SLA Notifications A Service Level Agreement (SLA) establishes a time constraint for completing tasks within a request role when a request is processed in dspConduct™. Users assigned to roles are notified through workflow messages when a time constraint is not met. A Designer performs the following tasks to set up SLA notifications for dspConduct™: dspConduct™ is delivered with a default calendar named dspConduct. Before SLAs can be configured in dspConduct™, this calendar must be configured for working days, working hours, and holidays specific to a client site, and dspConduct™ users must be added to the calendar in Common. https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Set_User_Workflow_Receipt_Preferences/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/Set_User_Workflow_Receipt_Preferences/ Set User Workflow Receipt Preferences dspConduct™ sends workflow messages to users who have access to a request when a request is created, canceled, deleted, finished, rejected or reset. Workflow messages can also be sent after a Final Finish package is created but fails to run, or when a post fails or succeeds. Workflow messages can be received via email, a notification in the DSP®, or both. By default, users receive workflow messages from dspConduct™ via email. https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/View_Default_Workflow_Messages/ Mon, 01 Jan 0001 00:00:00 +0000 https://hcloward.github.io/HCloward.github.io-syniti-hugo/dspConduct/Config/View_Default_Workflow_Messages/ View Default Workflow Messages dspConduct™ is installed with default workflow messages and the processing to send these messages. By default, dspConduct™ sends workflow messages to users who have access to a request when a request is created, canceled, deleted, finished, rejected or reset. A user can view the default messages that are delivered with dspConduct™ but cannot change the default messages themselves. Default messages are used as the starting point for Category Language-specific messages which may be edited.