Hi Erin,

You can search for the person id of the authorized person for the monitor schedule via the app param called ‘INTEGRATION_MONITOR_PERSON_ID’ though.And the password of that particular person should be the value of the app param called ‘INTEGRATION_MONITOR_PASSWORD’ though.

Thanks,

Induwari

How does the Auth. Person ID field of the Integration Monitor Instance screen?  Which overrides which?

Hi erin,

Normally for a monitor schedule to work properly, the person id in the monitor instance screen should be equal to the value of the app param called ‘INTEGRATION_MONITOR_PERSON_ID’. Basically the values should be same..And the value comes under the app param called ‘INTEGRATION_MONITOR_PERSON_ID’ is the value you should concern about..

And the person id we are putting as the value of the app param called “INTEGRATION_MONITOR_PERSON_ID’ should be consists of below requirements, for the monitor schedules to perform their expected behavior though..

1. Person should be an ACTIVE user
2. person should consists of his license type as STUDIO license
3. Person should be an ADMIN user 

Thanks,

Induwari 

The Auth. Person ID on the Instance existed before the App Param did - so the values could be different, although it’s understood they should be the same.  So what is the hierarchy?  App Param is used if defined - Instance is used if App Param is not defined - or ?

What is the reason for the STUDIO license type requirement (2)?  I understood integrations require only a MESSAGE license type.

What is meant by “ADMIN user” (3)?