Preparing Databases on Personify 7.1.2 - 7.3.1 for Mobile

If your organization currently runs on a version of Personify before 7.3.0 SP2, preparing the database includes additional steps related to Personify items, Mobile Stored Procedures, and e-Business items.

Personify Items Required

The lists below indicates the Personify items included in the Personify 7.3.1 version that DO NOT exist in the associated earlier Personify version.

You need to add these items to your application in order to integrate the Personify Mobile application with your database.

To add each one, run the related script available in the 7.3.1 release package.

No code retrofit or recompiling is necessary after running the script.

Personify 7.1.2

·            Stored Procedures

o           GetProductPrice_FN

o           GetDefaultRateStructure_FN

o           GetDefaultRateCode_FN

·            Tables

o           NTS_MOBILE_NOTIFICATION_MESSAGE

o           PRODUCT_MOBILE_CONTROL

o           PRODUCT_MOBILE_IMAGES

·            Set Up Date in App Codes

o           New code <MOBILE> for Type <ORDER_METHOD>

o           New type <PROD_MOBILE_IMAGE_SIZE> and its related codes

·            New Screens

o           ProductMobileControl.xml

Personify 7.1.3 - 7.3.0

·            Tables

o           NTS_MOBILE_NOTIFICATION_MESSAGE

o           PRODUCT_MOBILE_CONTROL

o           PRODUCT_MOBILE_IMAGES

·            Set Up Date in App Codes

o           New code <MOBILE> for Type <ORDER_METHOD>

o           New type <PROD_MOBILE_IMAGE_SIZE> and its related codes

·            New Screens

o           ProductMobileControl.xml

Mobile Stored Procedure Changes Required

Some of the Personify Mobile stored procedures need to be modified in order to work with versions of Personify earlier than 7.3.1.

The list below indicates the issue(s) related to each Mobile stored procedure for the Personify version and a solution of how to modify the stored procedure to make it compatible with your Personify version. Each solution listed for your Personify version must be executed.

Personify 7.1.2:

MOBILE_GET_EMPLOYEE_LIST

MOBILE_GET_RELATIONSHIPS

ISSUE: CUS_RELATIONSHIP.ACTIVE_FLAG does not exist.
SOLUTION: Make the following change in 2 places in the SP.
Comment out  --   C.ACTIVE_FLAG = 'Y'
Instead add --   (C.BEGIN_DATE<=getdate() AND
  (C.END_DATE IS NULL OR
    C.END_DATE>=dateadd(day,(0),datediff(day,(0),getdate()))))"

MOBILE_GET_MTG_LIST

ISSUE: MTG_PARENT_PRODUCT_TRACK does not exist. We added this table in 7.2.0 where we changed the logic on how meeting tracks worked.

SOLUTION: Remove: LEFT OUTER JOIN dbo.MTG_PARENT_PRODUCT_TRACK MPT on MPT.PRODUCT_ID = P.PRODUCT_ID
In the select clause replace
, MPT.SESSION_TRACK_CODE
 , MPT.SESSION_SUMMARY
WITH
, MP.SESSION_TRACK_CODE
 ,  MP.SESSION_TRACK_CODE AS SESSION_SUMMARY"

MOBILE_GET_PROFILE

MOBILE_GET_USER_CREDENTIALS

MOBILE_GET_USER_CREDENTIALS

ISSUE 1: CUSTOMER.Currency_Code does not exist

SOLUTION: Replace C.CURRENCY_CODE with ""USD"" as CURRENCY_CODE. We are not using Currency Code in the mobile app yet. "

ISSUE 2: CUSTOMER_ADDRESS.Latitude, Longitude do not exist

SOLUTION: Replace with 0 as latitude, 0 as longitude"

Personify 7.1.3:

MOBILE_GET_EMPLOYEE_LIST

MOBILE_GET_RELATIONSHIPS

ISSUE: CUS_RELATIONSHIP.ACTIVE_FLAG does not exist.

SOLUTION: Make the following change in 2 places in the SP.
Comment out  --   C.ACTIVE_FLAG = 'Y'
Instead add --   (C.BEGIN_DATE<=getdate() AND
  (C.END_DATE IS NULL OR
    C.END_DATE>=dateadd(day,(0),datediff(day,(0),getdate()))))"

MOBILE_GET_MTG_LIST

ISSUE: MTG_PARENT_PRODUCT_TRACK does not exist. We added this table in 7.2.0 where we changed the logic on how meeting tracks worked.

SOLUTION: Remove: LEFT OUTER JOIN dbo.MTG_PARENT_PRODUCT_TRACK MPT on MPT.PRODUCT_ID = P.PRODUCT_ID
In the select clause replace
, MPT.SESSION_TRACK_CODE
 , MPT.SESSION_SUMMARY
WITH
, MP.SESSION_TRACK_CODE
 ,  MP.SESSION_TRACK_CODE AS SESSION_SUMMARY"

MOBILE_GET_PROFILE

MOBILE_GET_USER_CREDENTIALS

MOBILE_GET_USER_CREDENTIALS

ISSUE 2: CUSTOMER_ADDRESS.Latitude, Longitude do not exist

SOLUTION: Replace with 0 as latitude, 0 as longitude"

Personify 7.2.0 - 7.2.1:

MOBILE_GET_EMPLOYEE_LIST

MOBILE_GET_RELATIONSHIPS

ISSUE: CUS_RELATIONSHIP.ACTIVE_FLAG does not exist.

SOLUTION: Make the following change in 2 places in the SP.
Comment out  --   C.ACTIVE_FLAG = 'Y'
Instead add --   (C.BEGIN_DATE<=getdate() AND
  (C.END_DATE IS NULL OR
    C.END_DATE>=dateadd(day,(0),datediff(day,(0),getdate()))))"

No code change is required for Personify 7.2.2 to 7.3.0.

e-Business Items Required

For configuring the e-Business website to work with the Personify Mobile application, you need to complete following changes for all versions prior to 7.3.1.    

·            New Module - Personify.LoginMobile

o           Recompile the web part in the required version.

o           Recompile Login Manager after adding one method to LoginManager class.

·            New Web Method - PersonifyShoppingCart.asmx

o           Add one web method to the web service, then recompile the web service.
Web Method Name: GetShoppingCartSummary

·            ShoppingCartMobileTemplate

o           Take the template as it is from Personify 7.3.1 and deploy it on your website.

·            Install the Personify MobiNuke web module on your website.

·            Modify the Personify_ShoppingCartGet stored procedure.

o           In the “where” clause add the condition <AND ISNULL([OrderNo],'')= ''>.
Make sure that order number column exists in the Personify_shoppingCart table. If it does not, there is no need to make this change.

If you organization decides to use the Single Sign On Web Service, you need to complete the following changes for all versions prior to 7.3.1.

·            Replace the "TIMSSSSO.Web.dll.
This is because we have added one new web method to the SSO Web Service.

o           Web Method Name: CustomerAuthenticateAndGetId

·            Add the new Stored Procedure created in SSO database

o           Stored Procedure Name: CustomerAuthenticateAndGetId"