Defining Dynamics Cloud Office 365 instances

Prerequisites

• Login credentials to the Quality Clouds portal – https://portal.qualityclouds.com/
• (optionally) the Client ID for Dynamics CRM. For details, see Step 1a on Setting up Office 365 instance.
• Git credentials and repository information

Setting up your instances #

In order to be able to scan your instances, you need to point Quality Clouds to them.

→ To create an instance in Quality Clouds #

1. Login to the Quality Clouds portal at https://portal.qualityclouds.com/.
2. Go to Account > Instances section.
3. Select the O365 tab (if you use several SaaS with Quality Clouds), and click the + (add instance) button.
4. Select Office Dynamics Cloud , and fill in the following information:
   • Description -Short and meaningful description of the instance. For example: MyCompany UAT
   • URL – URL of the Salesforce instance. This is descriptive only, and normally it will be pre-filled during the onboarding process. The Org which will be scanned is determined by the access credentials (Key and Secret). The Org Id will be extracted on the first scan and displayed in the views.
   • Tenant id: identifier for the org in Azure.
   • Client ID: An application identifier for the authenticator you register on your cloud, which will be used to access the instance
   • Client Secret: The secret generated by the platform for that authenticator application (similar to a password)
   • Environment – Environment type of the instance. This is used to add descriptive context to your instance.
   • Go-live Date – Date on which the instance was first started, serves as a baseline for Org changes.
   • Tags –  Use tags to add specific information for better instance recognition.
     
5. Click Save. 

→ Configure the Quality Gates #

1. When setting or editing an instance, click on the ‘Quality Gates’ tab.
2. Enable the Quality Gates toggle.
3. Add the Activation Date.
4. Configure the Blocking rules table and smart tagging.
5. Click ‘Save‘.

Click here to learn how Quality Gates work.

→ Configure the Peer Review #

1. When setting or editing an instance, click on the ‘Peer Review’ tab.
2. Enable the Peer Review toggle.
3. Select when to get notified when Peer Reviews are pending: None, Daily, Weekly or Monthly.
4. In the Peer Review Workflow section select ‘Write Off assignation’:
   • Manual Assign
   • Auto Assign
   • Developer Assign
5. Select the Default assignee email on the dropdown menu. Enable it if you want the default assignee to be notified when a write-off is assigned.
6. Enable or disable the Source Code toggle.
7. Click ‘Save‘.

• Manual Assign will hide the Default Assignee drop-down menu. 
• Auto Assign will show the Default Assignee and there won’t be any other option than to select one person from the list.