RegoXchange
  • Based on the pre-determined schedule frequency, this job will send an email to Project Managers that have a project meeting the criteria of: project(s) are active and scheduled finish date is less than the current date. This serves as a reminder to Project Managers to keep their schedules true. The contents of the email include a message indicating the project manager has at least one project meeting this criteria and a table indicating the Project ID, Project Name and Scheduled Finish Date.
  • The Enhanced Time Tracking Stalker – RM workflow process automatically sends a single email to Resource Managers which contains a list of any of their resources that have not submitted their timesheet for a prior open time period.  The email informs the RM if their resources are submitting their timesheets on time.  The email includes a table that provides this information for each resource: Resource Name, Time Period, Timesheet Status and Total Hours saved on the timesheet with links to the timesheet in the Modern User Experience of Clarity. These notifications will help to ensure that time is being posted and approved in a timely manner.
  • This grid portlet shows the OBS name and ID along with the associated hierarchy, both as an aggregated view along with each of the levels broken out. The table below describes the available filter fields in the portlet.
    Column Label Description
    Branch Branch of the OBS
    OBS Type OBS to use
    OBS Path Path of the OBS
  • This portlet displays list of resources with OBS rights. This would be helpful for admins to know if a user can perform any actions on object instances of an OBS.
  • Are you starting a resource management implementation, or do you want to compare how you are using these functions vs. others or best practices? In this class we will discuss some best practices from successful customers.
  • What integrations are the most requested and the most utilized? This class will review the most common interfaces to and from Clarity, including best practice use cases and lessons learned from real implementations.
  • 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 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.
  • Connect with user and get familiar with them via Office 365/Azure Profile photos synced with the Clarity PPM Avatars. This is a good way to collaborate with the team and users for any quick update or interaction. This is a scheduled process in Clarity named Sync Profile Photo from Office 365 and will be scheduled to run as a job. When the process is executed, it will be setting the Microsoft O365 profile photo into the users Avatar photo in Clarity PPM and optionally, sync custom attribute of the Resource with profile photo, which can be used for quick identification of the user. Sync Process come with some parameters for the Support team, which they can use as per there environment configurations. These some important Gel parameters for quick configuration are:
    • msProfilePicField : Custom Resource Field to store Photo, if not provided process will skip syncing the custom field.
    • msTenantId: Microsoft Azure Tenant Id
    • msClientId:  Microsoft Azure Application client Id
    • msClientSecret:  Microsoft Azure Application client Secret
    • msTeamPhotoSize: Define size of the photo to be fetched
    • syncPPMAvatar: Parameter to Sync PPM User Avatar photo from MS Team
    Please note, Azure Application Registration is required. To setup an Azure Application: https://learn.microsoft.com/en-us/azure/healthcare-apis/register-application The application requires the permissions outlined on this link to retrieve the pictures: https://learn.microsoft.com/en-us/graph/api/profilephoto-get?view=graph-rest-1.0 Use it along with RegoXchange – MS Teams link to seamlessly have a clickable link to MS Teams Conversations
  • The Audit Trail portlet displays information about audited attributes.  It is nearly identical to the view and functionality of the “Global Audit Trail” offering on the admin side.  It offers filters for the Object ID (resource internal id, project internal id, etc.), Object Name (Jim Brown, Project A, etc.), Changed By, a date range for the changed date and the operation of the change.  It is capable of reporting on the following:
    • Object (Resource, Project, etc.)
    • Object Name (Jim Brown, Project A, etc.)
    • Parent Name (if the object were a sub-object)
    • Attribute code (the attribute id from the attributes list on the object)
    • Operation (Update, Insert, Delete)
    • Changed By
    • Old Value
    • New Value
    • Date Changed
  • This tip with show you the html needed to add a JasperSoft report to a CA PPM HTML portlet.
  • This technical trick provides a supported method for removing team members from a project programmatically.  This is a XOG-based solution that might be called by a gel script in a process workflow.  Limitation is that the resource must NOT have actuals booked.
Go to Top