Crowd Wisdom Initial Setup Help

Once you've gone through the pages below, you can use this page as a quick cheat sheet to make sure you did everything you're supposed to do to get the integration up and running. 

Changes to Make in Aptify

Integration System Entity

  1. Open the Integration System entity.

  2. Open the Integration Password field.

  3. Go to Security tab, click on Encrypt Data and set security key ID 1:

    image-20230104-135415.png

  4. Click OK

  5. Open the Callback Password field.

  6. Go to Security tab, click on Encrypt Data and set security key ID 3 (the hash one):
    image-20230104-135528.png

  7. Click OK

  8. Save the entity.

Emails setup (optional)

If emails need to be sent when a person registers/unregisters, then we can enable the event handler that gets installed as part of the unpacking process and we can set up the message templates that also get installed.

This is optional since a client might already have templates that get sent when a person subscribes or unsubscribes.

First, look under Messaging Administration > Message Templates to find the IDs of the message templates that were installed. Because each client might have different templates setup, when the CM tool unpacks the LMS templates, the IDs could be different. For example, these are the IDs from my local machine.

image-20230104-141842.png

We will use these IDs in the integration system attributes.

Now, under Process Pipeline > Event Handlers, find:

image-20230104-141949.png

And make sure it’s enabled.

Integration System record

Open the CrowdWisdom Integration System record.

  1. Fields:

    1. Integration Password: given by Crowdwisdom (usually looks like a GUID).

    2. Integration Password Security Key: ID of key used to encrypt the integration PWD (usually ID 1)

    3. Callback Password: ONLY used when integrating using classic eBiz. This can be anything and is provided by Aptify to CW. CW will use this PWD to authenticate against the classic eBiz endpoints.

    4. Callback Password Security Key: ID of key used to encrypt the callback PWD (usually ID 3 - the hash one)

    5. Integration System Attributes:

      1. URL: provided by CW. I believe it’s usually: https://www.precrowdwisdom.com/diweb/ws/integration/v1

      2. username: provided by CW

      3. systemId: provided by CW (i’ve noticed that it’s sometimes the same as the username, but not all the time).

      4. callBackUsername: ONLY used when integrating using classic eBiz. This is the username that CW will use in conjunction with the callback PWD to authenticate against the classic eBiz endpoints. Defaults to ‘Test’ but can be changed to anything.

      5. subscribeMessageTemplateId: ID of the LMS Subscribe Email template.

      6. ubsubscribeMessageTemplateId: ID of the LMS Unsubscribe Email template.

New attributes:

  • Later versions of the Aptify.LMS assembly can use these three optional attributes.

Name

Value

Description

productMappings

[
{
"Type":"Meetings",
"Mappings":{
"Title":"MeetingTitle",
"Description":"VerboseDescription",
"StartDate":"StartDate",
"EndDate":"EndDate"
}
},
{
"Type":"General",
"Mappings":{
"Title":"Name",
"Description":"Description",
"StartDate":"DateAvailable",
"EndDate":"AvailableUntil"
}
}
]

Allows sending different fields from different product types to the title, description, start and end date field of CW.

If not present, Aptify will just send:

  • Product Name

  • Product Description

  • Date Available

  • Available Until

productCategoryMappings

Meetings:Event| Conferences:Publication| Educational Seminars:Publication

Allows more granular mapping of products in Aptify to types in CW. Instead of using the Type, we use the Category.

If not present, Aptify will just use the Type mapping.

sendDescription

true

If set to true, will send the description to CW. Mostly usable if the description field has been modified in CW and we don’t want to override it with the description data from Aptify.

If not present, Aptify will default to true.

Things to Provide to CW:

CW will hit Aptify only when a user finishes a course. Depending on the site the client has (classic eBiz vs eBiz6), the endpoints and authentication changes.

Classic Ebiz:

Deployment Cheat Sheet:

  • 2 new DLLs into eBiz bin folder

    • Aptify.LMS

    • Aptify.Integrations

  • LMSEndpoints.asmx in Web Services folder.

  • LMSEdnpoints.vb in App_Code folder.

  • Web.config, need to add:

     
    <add name="HttpPost" /> So it looks like:
    • image-20230814-141614.png

More information here: Configuring Crowd Wisdom Integration on classic e-Business

  • LMS System ID: ID of the integration system record. Usually, ID 1.

  • Web Service Base URL: this is the base URL of the classic eBiz where the web service lives.

  • Web Service Password: callback PWD

  • Web Service Username: callback username

eBiz 6/7

Deployment Cheat Sheet:

  • 2 new DLLs into SOA bin folder

    • Aptify.LMS

    • Aptify.Integrations

  • LMSIntegration folder that contains LMSIntegrationEndpoint.json

More info here: Configuring Crowd Wisdom Integration on e-Business 6/7

Need a new web user group called ‘LMS Vendor’. Only web users with this group will be able to access the eBiz6/7 endpoints as there is security defined.

A web user will need to be created just for use with CW. Based on the documentation linked above, this web user will need to be linked to the ‘LMS Vendor’.

  • LMS System ID: ID of the integration system record. Usually, ID 1.

  • Web Service Base URL: this is the base URL of eBiz 6.

  • Web Service Password: web user’s username

  • Web Service Username: web user PWD

Aptify Web

Deployment Cheat Sheet:

  • 2 new DLLs into SOA bin folder

    • Aptify.LMS

    • Aptify.Integrations

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.