Skip to main content

Hi Experts,

I wanted to setup contacts so that they appear in mobile client (under main menu ‘Contacts’). I am trying to figure out the behavior of application parameter CONTACT_LIST_TYPE which has 3 values (service organization, Company and Site).

If I refer to help docs it says(for option ‘Service organization’) I should have a contact list in service organization, but I could not find such list in service organizations or in its delivery units? (can it be the access group? I tried but not). In this test I got few contacts synced, but cannot figure out a particular pattern (all my resources are in one resource group and that resource group is a primary resource group. All of them are connected to same service organization and same site)

Then I check option ‘company’, I get some contacts synced (different to above test) to the device, but none of them register in company as contacts (not even in addresses). If I use option ‘Site’, I did not get any contacts synced.

Can someone explain this bit more please?

Thank you,

Roshan

Help Doc:

 

Hi ,

If the app param is set to ‘service organization’,  the system retrieves the resources connected to the logged-on user's Service Organization through the service organization connections in Resource Details. The resources should have a primary parent resource group and a valid mobile user connected.

For ‘Site’,  the system looks at the user’s Primary site as defined in Resource Details.

For ‘Company’, the system looks at user’s company connections where the user is also a valid mobile user.  

Note that, an incorrect dependancy to the app parameter ‘SERVICE_REQUEST_FOR_NEW_WORK’ has been corrected in 24R2. It may be worth checking if you still experience issues.

Regards, 

Uthpala

Hi ,

If the app param is set to ‘service organization’,  the system retrieves the resources connected to the logged-on user's Service Organization through the service organization connections in Resource Details. The resources should have a primary parent resource group and a valid mobile user connected.

For ‘Site’,  the system looks at the user’s Primary site as defined in Resource Details.

For ‘Company’, the system looks at user’s company connections where the user is also a valid mobile user.  

Note that, an incorrect dependancy to the app parameter ‘SERVICE_REQUEST_FOR_NEW_WORK’ has been corrected in 24R2. It may be worth checking if you still experience issues.

Regards, 

Uthpala

Thank you Uthpala for the response.

In case if you can elaborate more on site and company connections would be great. Because it is not clear how the link is formed between logged in mobile user and sites/companies. If you setup data and try this you might also find its behavior as confusing.

 

Also what is the connection between SERVICE_REQUEST_FOR_NEW_WORK (creating new request in mobile) and contact list ?

 

Hi Roshan,

Clarifying the above further :

Resource should have a primary parent group connected.

When App parameter is set to  ‘Site’ : Logged in User’s primary site is the ‘Primary Site’  as defined in the Resource Details\Maintenenace-Service\Site Settings. 

When App parameter is set to  ‘Company’ : Logged in user’s company connections are the Company and Site Connections under Resource Details\Connections

Only the app parameter ‘Contact_LIST_TYPE’ is applicable.  The other  (SERVICE_REQUEST_FOR_NEW_WORK) is a defect and has been corrected in the latest track (24R2). If you find any issues related to that in previous tracks, please report a defect.

I think we need to improve documentation around this functionality. R&D will look into it.

Regards,

Uthpala

Hi Roshan,

Clarifying the above further :

Resource should have a primary parent group connected.

When App parameter is set to  ‘Site’ : Logged in User’s primary site is the ‘Primary Site’  as defined in the Resource Details\Maintenenace-Service\Site Settings. 

When App parameter is set to  ‘Company’ : Logged in user’s company connections are the Company and Site Connections under Resource Details\Connections

Only the app parameter ‘Contact_LIST_TYPE’ is applicable.  The other  (SERVICE_REQUEST_FOR_NEW_WORK) is a defect and has been corrected in the latest track (24R2). If you find any issues related to that in previous tracks, please report a defect.

I think we need to improve documentation around this functionality. R&D will look into it.

Regards,

Uthpala

Thank you Uthpala for the response. I will check this in 24R2

Reply


Terms & ConditionsCookie settings