Invocation of standard services

Once declared in service meta information file and implemented using either RESTful or Functional approach, Asset Picker invokes it in the following scenarios:
  • Simple Search (simple-search)

    Whenever Asset Picker receives content or asset search request from its client application against target system, it invokes the simple-search service implemented for respective system. Asset Picker provides necessary input to the simple-search service upon invocation. Search items received from simple-search service are then returned to the client application. Identification of the target system happens based on the systemId property used in the service meta information file and the corresponding System Identifier setting in Unica Platform populated during the target system onboarding. This service must be implemented by the plugin, else the content search request ends up in 404 response to the client application.

  • Resource Loader (resource-loader)

    The resource-loader service is executed by Asset Picker only when indirect (or authenticated) access needs to be made to the search item on target system. With the absence of a direct URL to an individual search item on the target system, the resource-loader service can be implemented by the plugin. Being an optional service, Asset Picker automatically recognizes if the resource-loader implementation exists for the target system and invokes it accordingly.

  • Asset Selection Callback (asset-selection-callback)

    Asset Picker executes this service for the target system when the client application selects one of the search items returned by the simple-search service. Because the service is optional, Asset Picker can automatically recognize the existence of this service and invoke accordingly.