787 results
-
The Update Email Ids workflow sets all users’ email addresses to non-working by appending a “ZZZZ” to the end of the email address. This process is used for when there are refreshes to your Development or Testing environments and do not want emails going to users. When complete, the log will display the total amount of email addresses updated. A second process is included in this workflow that will revert the email addresses to remove the “ZZZZ” added in the first workflow. In some instances, the process may be run in error, or you may want to send emails from a Development or Testing environment; using this second process you will be able to enable all emails again. -
The Update Email Ids workflow sets all users’ email addresses to non-working by appending a “ZZZZ” to the end of the email address. This process is used for when there are refreshes to your Development or Testing environments and do not want emails going to users. When complete, the log will display the total amount of email addresses updated. A second process is included in this workflow that will revert the email addresses to remove the “ZZZZ” added in the first workflow. In some instances, the process may be run in error, or you may want to send emails from a Development or Testing environment; using this second process you will be able to enable all emails again.
-
The Update Email Ids workflow sets all users’ email addresses to non-working by appending a “ZZZZ” to the end of the email address. This process is used for when there are refreshes to your Development or Testing environments and do not want emails going to users. When complete, the log will display the total amount of email addresses updated. A second process is included in this workflow that will revert the email addresses to remove the “ZZZZ” added in the first workflow. In some instances, the process may be run in error, or you may want to send emails from a Development or Testing environment; using this second process you will be able to enable all emails again.
-
The Users Logged In portlet displays all users logged into the system. This portlet is helpful to determine the capacity during peak times, users still working before downtime, and the ability to view users logged in during the day. The portlet will display the resource, ID, OBS unit, OBS path, and when the user’s session was last updated. -
The Users Logged In portlet displays all users logged into the system. This portlet is helpful to determine the capacity during peak times, users still working before downtime, and the ability to view users logged in during the day. The portlet will display the resource, ID, OBS unit, OBS path, and when the user’s session was last updated.
-
The Users Logged In portlet displays all users logged into the system. This portlet is helpful to determine the capacity during peak times, users still working before downtime, and the ability to view users logged in during the day. The portlet will display the resource, ID, OBS unit, OBS path, and when the user’s session was last updated.
-
The Auto-Approve Old Timesheets workflow process can be run through the "Execute a Process" job and may be used to quickly close out timesheets for a specified timeframe for period closure. The workflow will execute a query that will automatically approve ALL (no matter the status of the timesheet) timesheets that have a time period start date before the Approve Date specified within the process itself. -
The Auto-Approve Old Timesheets workflow process can be run through the "Execute a Process" job and may be used to quickly close out timesheets for a specified timeframe for period closure. The workflow will execute a query that will automatically approve ALL (no matter the status of the timesheet) timesheets that have a time period start date before the Approve Date specified within the process itself.
-
The Auto-Approve Old Timesheets workflow process can be run through the "Execute a Process" job and may be used to quickly close out timesheets for a specified timeframe for period closure. The workflow will execute a query that will automatically approve ALL (no matter the status of the timesheet) timesheets that have a time period start date before the Approve Date specified within the process itself.
-
The Turn off Notifications process disables all Email, SMS and Alerts notifications for all users. This process is helpful if users would not like to receive emails from the system regarding actions items, timesheet submissions, etc. The script may be modified to include all users or all users that have been created within the last day. -
The Turn off Notifications process disables all Email, SMS and Alerts notifications for all users. This process is helpful if users would not like to receive emails from the system regarding actions items, timesheet submissions, etc. The script may be modified to include all users or all users that have been created within the last day.
-
The Turn off Notifications process disables all Email, SMS and Alerts notifications for all users. This process is helpful if users would not like to receive emails from the system regarding actions items, timesheet submissions, etc. The script may be modified to include all users or all users that have been created within the last day.
