Versions Compared

Version Old Version 3 New Version 4
Changes made by

admin (Deactivated)

admin (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Certain additional steps are required to successfully complete the Mobile Point of Sale Implementation. Included below is a list of IIS configurations, Aptify configurations, and other settings required to support the Mobile Point of Sale Application:

Anchor
_

...

objRep
_

...

objRep
Object Repository Sync

The listed assemblies should be removed from the framework bin located in the framework website folders. Following is the list of dlls that should be removed (if present) from the framework bin folder:

  • CertificateImportWizard__c.dll
  • ExpoCADShared.dll
  • ExpoCADBoothSynch.dll
  • ExpoCADAPIWrapper.dll
  • Expoapi.dll
  • ConfigManifestForm.dll
  • CertificatePrintObject.dll
  • TemporaryComponent.dll
  • IAptifyWebBoundControls.dll
  • MeetingTransferLayoutControl.dll

Anchor
_

...

iisConfig
_

...

iisConfig
IIS Configurations

Configure SSL for both the web service sites

...

  1. In IIS Manager, select the Application Pools node.
  2. From the Application Pools list, select the application pool created for Point Of Sale and verify the identity is configured to use trusted user's credentials.
  3. Select the application pool created for AptifyFramework and configure the identity to run under the Local System context by selecting the advanced settings on the right hand pane.

    Application Pool Settings

Anchor
_

...

aptifyConfig
_

...

aptifyConfig
Aptify Configurations

This section describes the configuration required in Aptify to support the Mobile Point of Sales application.

  1. SMTP Configuration: If you do not have a messaging system configured to send emails, refer to the steps in the " Messaging Administration " chapter of the Aptify 5.5.1 Administration Guide to  to configure a messaging system that POS will use to send receipts.
  2. Update the Process flow configuration for receipt email.
    1. At the end of a POS Order on the app, a user has the option to send an email receipt. In order to successfully send an email and format the message appropriately, verify the configuration of the properties in the process flow as specified below.
      1. Open the POS Send Receipt process flow in the Aptify system.
      2. Select the Create Message Runs Record rule block from the Process Flow designer.
      3. On the right hand side of the pane, select the Properties tab.
      4. In this tab, make sure the following properties are configured to use the appropriate record IDs from the Messaging Administration application: MessageSystemID, MessageSourceID, and MessageTemplateID. MessageSystemID should be the DotNet or SMTP DotNet messaging system that will be used for sending out emails. MessageSourceID should be the Message Source corresponding to Orders. MessageTemplateID should be set to the message template that you want to use for sending out POS Receipt emails.

        Process Flow Properties

  3. Confirm that the Message Runs Event Handler is active.
    1. On the Aptify smart client, select the Process Pipeline application.
    2. Select the Event Handler service.
    3. Open a view with all event handlers.
    4. Open the Message Runs event and make sure it is set to Active status.

      Message Runs Setting 

Anchor
_

...

POS
_

...

POS
POS Event Setup

Follow these steps to create an Event in Aptify that corresponds to where your organization will use the POS iPad application:

  1. In the Aptify Smart Client, select the Point Of Sale application.
  2. Select the Events service, and open a new record to create a POS event.
  3. On the General tab, enter the following:
    1. Event Name: Enter the name of the Event where you plan to use the POS iPad application.
      1. POS supports the creation of multiple events.
      2. Events set to enabled are available on the iPad.
    2. Description: Enter a description of the event.
    3. Status: Set the status to Active for the event you want to enable.

    4. Timeout Period: Time in minutes after which the token/session with the app will expire. This is a non-editable field on the Event form. Timeout period can be changed from the Timeout attribute of 'Database Token' record, under the Token Provider service.

      Note

      Please ensure that the timeout for the POS and SOA app pools on the IIS is greater than or equal to the timeout period set for token expiration. By default, IIS sets the app pool timeout setting to 20 minutes. Follow the steps given in the Additional Information section for changing the app pool Timeout setting and Timeout attribute for Token Provider.

    5. Inventory Location: Enter your default inventory location. This inventory location will be used for depleting inventory for all "Pay-and-Carry" Orders. If the product is not available in that inventory location then it will be depleted from its default inventory location. For To Be Shipped Orders, inventory will always be depleted from product's default inventory location.

    6. Location: Enter the location for the event. This location determines the ship to location for all the "Pay-and-Carry" orders.

    7. Campaign: If applicable, enter a campaign to apply to the orders placed for this event through the POS app.

    8. Start Date: Enter the POS Event Start Date.

    9. End Date: Enter the POS Event End Date.

    10. Meeting: Enter the meeting associated with the Event. All the people who are registered for the meeting appear as attendees on the iPad, using the GetAttendees as the attendee view.

    11. Sales Tax Rate: This field is reserved for future use.

    12. Guest ID: Enter the generic Person ID to be used for customers checking out as a guest.

    13. Organization: Enter the name of the Organization to be used for all the orders placed for this event through POS app.

    14. Is Price Override Allowed: Check this box, to allow a POS user to override the price of the product from the iPad. POS User can only override the price of a product, if this property is checked as well as the product price override is allowed.

    15. Use Catalog Price: Catalog Price is the highest price of the product from the price matrix. Enabling this feature will use the catalog price for every user. Uncheck this box, to disable catalog pricing and use any specified member and non-member pricing instead. Irrespective of the value of this property, the first page on the POS app will always display the catalog price. But based on the value of this property it will recalculate and select the appropriate price on the checkout page of POS app.

    16. DefaultOrderSourceID: This field is reserved for future use. Default Order source at present can be set from the POS Orders entity's configuration tab. Please refer to POS Order Entity Configuration section of this guide. Please set the same value in this field as set in the POS Orders entity configuration.

    17. ProductCatalogView: Enter the name of the view that includes all the products that will be available for sale at the event using the POS app. Verify the fields of the view entered are exactly same as that of the ProductCatalog view (This is a baseline view in the POS Products service owned by sa.) which is under POS Products service.

    18. AttendeesView: Enter the name of the view that includes all persons available for an event on the POS app. Verify that the fields of the view are exactly same as that of the GetAttendees view (This is baseline view in the POS Attendees service owned by sa.) under the POS Attendees service. Please ensure that Product Catalog and Attendees views have unique names and no spaces.

      POS Event Form
       

  4. Select the POS Events Payment Types tab and add the payment types that will be accepted at the event. At a minimum, one payment type must be included each for cash, check, and credit card payment methods. Payment Types supported by POS are Cash, Check, Credit Card and Credit Card Reference Transaction.
     

    Note

    There cannot be more than one of same credit card type. If you enter multiple payment types that use the same credit card type, then the POS application will use the payment type with the lowest ID. In other words, for best results, there should not be two VISA credit card payment types or two MASTERCARD payment types.



    • Cash Control Batch can be set while adding Cash and Check payments. Please note that Cash Control Batch will not work for Credit Cards or Credit Card Reference Transaction payment types.

  5. Save the record to finish creating the POS event.

  6. Select POS Events Shipment Types tab and add the shipment types that you want to make available for the orders that are "To-be-Shipped". POS app user will be able to select any of the available shipment types, for "To-be-Shipped" orders. To set the default shipment types for "Pay-and-Carry" orders and "To-be-Shipped" orders, please refer to the POS Order Entity configuration section.

 

Anchor
_

...

POSorder
_

...

POSorder
POS Order Entity Configurations

Follow these steps to define a set of entity attributes for the POS Orders entity based on your system's configuration:

...

After completing the installation and post installation configuration steps, you should have a working web service and POS service to support the POS iPad app. Follow the instructions below to install the POS app on the iPad and create profiles for using the app.

Anchor
_

...

iPad
_

...

iPad
POS iPad App Installation and Configuration

Aptify will require requires two items for enabling POS on an iPad:

...