Last Mile Customer Portal¶
Before you configure the integration between IFS Cloud, PSO, and the Portal Studio Designer, take note of the following critical factors:
Integration Prerequisites¶
- Endpoint Availability: Ensure you have the correct URLs for both the PSO API and your IFS Cloud environment. The integration cannot function without active communication between these endpoints.
Credential Objects: You must create separate credential sets for each provider.
- PSO: Requires a
Customauthentication scheme. - IFS Cloud: Requires an
OAuth2.0-Passwordauthentication scheme. - Studio App Import: Always create your credentials before importing the Studio App from the App Store to ensure providers are linked correctly during the setup.
- PSO: Requires a
Configuration Precision¶
- Exact Naming: The Dataset Name in the Admin Configuration must be an exact character match to the dataset name residing in IFS Cloud.
- Placeholder Syntax: When setting up Global Action Sets to retrieve customer details, you must use the specific placeholder
TaskId(case-sensitive). Incorrect casing will prevent the PSO Event Hub from matching jobs to contacts. - Provider Mapping: Ensure you configure specific provider records (e.g.,
PersonHandling,RequestHandling) to enable task assignments and job allocations.
Timing and Synchronization¶
- Subscription Intervals: PSO subscriptions are valid for 24 hours. When setting the Scheduled Start Time, include a buffer of at least 15 minutes to account for system synchronization.
- Cache Latency: If you modify an existing dataset, the system requires a propagation delay of approximately 15 minutes before the changes take effect in the cache.
- Activation Order: Keep the Enable Configuration toggle OFF until all rules, providers, and customer detail actions are fully configured. Only enable it when you are ready to begin receiving live notifications.
Manual Post-Setup Tasks¶
- Survey Elements: The survey trigger at the end of the customer journey is not automated. You must manually configure the survey element within the LMCP application following the initial setup.
- Notification Rules: While rules are added automatically upon saving a dataset, you must verify that the triggers (Resource, ETA, or Status changes) align with your specific business communication logic.