Certificates - Workflow and statuses - j5 - 28.0 - Help - Hexagon

The following graphic illustrates the workflow that a certificate can go though as it moves from Drafting to Complete.

• This section explains the default statuses configured for certificates. If your workflow processes require different statuses, please contact your regional Hexagon j5 office.

• Only certificates in the Issued state can be viewed on j5 Mobile. However, all of the sections in the certificate can be viewed on j5 Mobile when it's in the Issued state.

The workflow moves through the following stages:

1. Click Add to create a certificate. The certificate’s first status is Drafting.

2. Any user that has editing rights in the Certificates module and Certificates sublog (refer to Default module permissions) can draft and edit the general details for the certificate. After the first section is saved and submitted, the certificate’s status changes to Requested. If the first section is revised, the status changes back to Drafting.

3. The user assigned to the Issuing Authority role confirms that all of the necessary controls have been put in place, configures the certificate’s Valid Until date, and issues the certificate. The certificate’s status changes to Issued.

   • If the Valid Until date is past while the certificate is in the Issued state, the certificate’s status changes from Issued to Expired.

4. To close and complete the certificate, the Performing Authority and the Issuing Authority confirm and sign that the worksite is clear and safe. The certificate’s status changes to Complete.