-
The Status Report Publish workflow process pushes values from the status report sub-object to the parent project object. The process is started when the user ticks the “Publish” Boolean field on the status report (custom field added). This workflow will update the project object with the overall status indicator, the status comment, the previous overall status, and the as of date. This eliminates the project manager having to update the fields in both the status report and the project overall. -
Are your reports and portlets performing well? This class will walk through specific SQL tuning tricks to make queries run faster, increase end-user satisfaction, and smooth-out system performance. This is an easy way to promote efficient future development and make a huge, positive impact on user experience. -
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 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 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 process must be run using the “Execute a Process” job. Job may be scheduled or run on-demand. Process pulls Availability Rate from the Availability blob for each resource, where blob is not null. Then it populates this value into a custom Daily Availability attribute (Number field with 2 decimals) on the Resource object. This field does not have to be displayed to be used for reporting. Because the OOB Availability Rate field is stored only in a blob, it is difficult to include in portlet or report output. The use of this custom attribute makes the value easily reportable. -
The Self Assign workflow process updates a selected resource field on an object based on someone checking a boolean field on the same object. Using this process, whomever is editing the object, will be placed in this field automatically eliminating the need for each user to come in and update the field manually. The field will run when the Boolean is ticked and the user saves the page. It is important to note that the page will need to be reloaded to see the changes reflected. This can be used as a fast way to self-assign yourself to an object - you can create a boolean field that is checked and have the process assign you to that item. -
The Self Assign workflow process updates a selected resource field on an object based on someone checking a boolean field on the same object. Using this process, whomever is editing the object, will be placed in this field automatically eliminating the need for each user to come in and update the field manually. The field will run when the Boolean is ticked and the user saves the page. It is important to note that the page will need to be reloaded to see the changes reflected. This can be used as a fast way to self-assign yourself to an object - you can create a boolean field that is checked and have the process assign you to that item.
-
The Scheduled Jobs Cleanup process removes all completed job instances that have run before a date set by the administrator. The administrator may use the gel parameter to update the amount of days since each job has run. Based on that date, the workflow will eliminate all jobs that have surpassed that threshold. This workflow helps administrators maintain the job logs and queue by eliminating jobs that users have potentially forgotten to remove on their own. -
The Scheduled Jobs Cleanup process removes all completed job instances that have run before a date set by the administrator. The administrator may use the gel parameter to update the amount of days since each job has run. Based on that date, the workflow will eliminate all jobs that have surpassed that threshold. This workflow helps administrators maintain the job logs and queue by eliminating jobs that users have potentially forgotten to remove on their own.
-
The Scheduled Jobs Cleanup process removes all completed job instances that have run before a date set by the administrator. The administrator may use the gel parameter to update the amount of days since each job has run. Based on that date, the workflow will eliminate all jobs that have surpassed that threshold. This workflow helps administrators maintain the job logs and queue by eliminating jobs that users have potentially forgotten to remove on their own.
-
This portlet shows the variance between the schedule finish and baseline finish for projects. The portlet also displays the schedule variance: {(Finish-Start) – (Baseline Finish-Baseline Start)}.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy