![]() ![]() ![]() ![]() ![]() ![]() ![]() |
There are some steps you must perform after you install HiPer for Retail before users can start using the application. Perform the following steps after you complete the steps in the Installation and Upgrade Guide for AquaLogic HiPer Workspace for Retail:
HiPer for Retail depends heavily on user properties. These properties include the hierarchical level of the user, the user's role, and the store name. You must create one or more Profile Web Services (PWSs) to import that information into the portal.
Note: | There is a sample PWS that can import the appropriate properties from an Excel file. |
You need to map User Extended Object Data (EOD) to HiPer-for-Retail-specific user properties. HiPer for Retail uses these properties to build the geographic hierarchy and the organizational hierarchy and to complete dynamic group selection. Here are the HiPer for Retail user properties you can map (bolded properties are required):
You must assign the activity rights in the portal to give your users access to HiPer for Retail features.
The following activity rights are available:
The following are some of the portal objects you might need to work with. They were created in the Application Spaces : HiPer portal folder when you imported the HiPer for Retail .pte files into the portal.
Synchronizes users with the dynamic notification lists in HiPer for Retail. The job runs nightly (it is process intensive). For more information, refer to Synchronize the Dynamic Notification Lists.
|
|
Builds the organizational hierarchy for each user in the HiPer for Retail application. For more information, refer to Synchronize the Flat Hierarchy.
|
|
Sends system and manual notifications. For more information, refer to Send Notifications.
|
|
Searches the Publisher repository and synchronizes the tips with the HiPer for Retail database. For more information, refer to Synchronize Tips.
|
|
Celequest reportlets can be added to the Summary page like any other portlet. Reportlets are Flash objects that can be embedded into a custom portlet. HiPer for Retail includes the following samples to help you create your own reportlets:
For more information on reportlets and how to set up the samples, refer to Celequest documentation.
![]() ![]() ![]() |