MosoMRM 1.85


				

Contents

Overview

(Release Date: 1/28/2013)

MosoMRM 1.85 includes a completely icon_new.gif layout of the Workstations configuration page, several refinements to the Scheduler functionality, and other enhancements to existing features and functionality:

Agreements Tab

When you click the Edit button on a Family or Corporate Agreement ONLY, the Member Agreement Update pop-up window displays. The purpose of this information is to ensure that you are aware of the current payment responsibilities and all of the associated Funding Source information. This window provides:

  • A list of all of the associated Funding Sources.
  • A section (gray) that displays:
    • The Percentage of Responsibility for the primary Member and the add-ons.
    • The current Funding Sources being used for this Agreement.
    • The add-on for whom you are currently editing the percentage of responsibility.

Check-In

Deny Reasons

The reasons that a Member or Customer was denied access at check-in are now being recorded. These reasons are not displayed on the User Interface but are recorded in the Check-In reports. The actual reasons however, can be viewed in the database tables ONLY.

Auto-Redeem Activities

This feature gives you the ability to auto-redeem an Activity at Check-In and immediately print the Activity redemption receipt.

For the print feature to be operable, make sure you select Yes in the following drop-down lists in the Workstations configuration:

  • Enable Print Applet
  • Print Redemption Rcpt (Receipt)
  • Redeem Scheduled Appt (Appointment)

These must be done in conjunction with configuring how many minutes prior and after the time of the scheduled Appointment you can check in and use the auto redeem feature in Check-In Configuration.

  • If you set both of these fields to 30-minutes, if you check in 30-minutes prior or after the scheduled start date of the Activity, it will be auto-redeemed and a receipt will be issued. Conversely, if you configured these same settings and you checked in 45-minutes prior to the Appointment time, the Activity would NOT auto-redeem.
  • If you configure both of the field to Zero (0) minutes, no auto-redemption will occur at Check-In.

Delegated Log-Out URL

This feature gives you the ability to redirect any logged in Users in an Authenticated session to a specific URL when logging out.

The Delegated Logout URL field has been added to Enterprise Security Configuration to configure which URL you will be directed to when logging out. The URL you enter must be http or https and can be set at the Enterprise level ONLY. Typically when logging out of MosoMRM, you are directed back to the standard MosoMRM Log-In page. When using this feature however, you are directed instead to the URL that you specify in Enterprise Security Configuration.

External Client Accounts

These are externally managed Accounts (Members or Organizations) that can be viewed in MosoMRM. These Accounts display in the User Interface with all of the features of a standard Member Profile but are read-only. Consequently, you no payments or adjustments can be made on the Account in MosoMRM, invoices can not be created, and none of the Account properties can be edited.

The account is also not displayed in any area of MosoMRM where a new entity can be created such as the Agreement Writer and POS but it will:

  • Have Status updates.
  • Be considered in the Accounts Receivable Aging report.
  • The Account Balance will display at Check-In and in Moso myClub.

External Flag for Agreements

An External flag is being added to indicate that this Agreement is being maintained externally from MosoMRM. This flag will NOT be visible on the User Interface and can only be accessed through the MosoMRM Import Utility or through a dual API call.

External Flag for Member Agreement Import

A column has been added to the AgreementsToImport table called FromExternal. You should set the new property on the MemberAgreement table called FromExternal based on this value.

External Funding Sources

This feature gives you more flexibility in integrating current, and creating new, Funding Sources for your Member/Customer Accounts.

An external flag (Yes or No) has been added for Funding Sources but will NOT be visible in the User Interface. This flag can only be accessed through the MosoMRM Import Utility or through an API call.

Heartbeat URL

The Heartbeat URL feature gives you the ability to keep sessions from timing out when using Delegated Authentication. The Heartbeat URL field has been added to Enterprise Security Configuration and is set at the Enterprise level ONLY. In turn, MosoMRM sends a request ("pings") every 60-seconds to the URL you specify in Enterprise Security Configuration for the purpose of keeping any or all remote sessions alive without interruption.

Invoice Import Utility

Additional fields have been added the Invoice Import Utility so you can set the expiration date for Activities during the invoice import.

If no expiration date is set, the expiration rules that were set at the item level will apply.

Moso myClub

Moso myClub "Deep Linking" into Scheduler - This gives you the ability to pass parameters into the Moso myClub scheduler for both Services and Events. This will allow external links to send traffic directly into a specific Event Date, or Service.

Receipt Messages

The Receipt Message you add in Item Setup displays at the bottom of a receipt in a POS transaction. The message is limited to 250 characters and will only be repeated once if that item is on multiple lines in the transaction.

Postal Code Required

A flag has been added to the Business Units configuration that gives you an option to require that a Postal/Zip Code be added before adding or saving any Funding Source, specifically a credit card. This will apply when adding a Funding Source on the:

If this check box is selected, it will be required that the Postal/Zip Code field on the Add/Edit Funding Source page be populated before saving the credit card. If it is not populated, as is the case with all other required fields in MosoMRM, the field will be red and a warning message will be thrown if you try and save the page.

Scheduler-Allowing Children as Attendees

The Children of Members can be the actual attendees for an Appointment or Event in MosoMRM and in Moso myClub.

The Attendee field has been added to the Add Registration pop-up window giving you the ability to select a Dependent, IF the Member (Customer field) has Children added to their Profile. If they do not, the field is inactive.

This also is available on the Create Appointment pop-up on the Scheduler. The Choose Attendee field will only display if you select a Member that has Children/Dependents on their Profile.

Suspension Details

When Suspending an Agreement or editing an existing or future Suspension, a Details section has been added outlining the specific details of the Suspension including:

  • The Type of Suspension, the Agreement to which it was applied, the Date of the Suspension and who performed the action.
  • Status (Active, Rescinded,Future)
  • Suspension Reasons
  • The End Date if applicable.

Workstations

The Workstations configuration page has been revamped to look more inline with other configuration pages. The page has been divided into two (2) sections with the basic information selections on the left and the feature selections on the right.

Two (2) additional configuration settings have been added-Print Redemption Rcpt (Receipt) and Redeem Scheduled Appt (Appointment)-giving you the ability to, in conjunction with other configuration settings, auto-redeem Activities at Check-In. (see above)

Resolved Issues

Reports & Launch Pad

4775 (NS:79847): The report folder icons now consistently display without issue.

New Reports

None

Updated Reports

(Alphabetical Order)

Activity History

  • The Service Provider now displays on the report if the Activity was redeemed through the Scheduler. (4850)
  • Reinstated Activities now display as a negative value. (4886)

Billing Batch Decline (4779, NS:79942)

  • The Decline Fees total in the Location Summary grouping is no longer reporting as double the correct amount.
  • The Decline Fees total when grouping by Member Detail vs. Location Summary are now reporting accurately.
  • The Current Balance column now lines up with the amounts in that column when report is exported to excel (Member Detail and Location Summary only).

Member Information

  • The 'option to show thumbnail of Member Picture' phrase has been removed from the Report description. This feature is not available in this report. (4932, NS:81268)

Rental Agreements

  • The Location grouping (default group) now reports the Agreements appropriately. (4943, NS:81355)

Activity Management

4778 (NS:79838): You can now redeem and/or schedule an Activity that does not expire (Value For= "Unlimited") without error.

4872 (NS:80798): The proper Service Provider now displays in Activity Management after booking an Appointment in the Scheduler. (NOTE: This was primarily occurring when an employee was also a customer. As a result there were two (2) party roles for a single PartyId from the database).

Agreement Templates

4875 (NS:80702): The PDF Agreement now displays the correct Sales Person that was added in the Agreement Writer.

Agreement Writer

4888/4965 (NS:80917): If a default payment option has not been selected (Perpetual, Installment or Paid-In-Full) has not been selected, one must be selected prior to proceeding to the next step.

  • The "To proceed, an option must be selected" required field message will display (red font).
  • Click that link, which will direct you back to the Bundle Setup page where you must select a default option.

Bundle Setup

4876 (NS:80373): The spelling error on the Add Installment Option button in the Installment Options window has been corrected.

Enterprise Security Configuration

When using Delegated Authentication:

  • An error message is no longer thrown when a non-admin User attempts to get a PIN Code. (4910)
  • All of the required fields now display properly on the Reset Password window, giving you the ability to cleanly reset your password. (4908)
  • The Save button is now inactive on the Edit Account window. (4918)

Events & Scheduler

The following options have been removed from Scheduler:

  • The "Mark as Not Paid" option from the Action Types drop-down list on the Appointment Details. (4871)
  • The "Anyone Available" option from the Choose Staff Member drop-down list when creating an Appointment. This will require you to select a specific Service Provider. (4877)

4740 (NS:79588): Inactive items no longer display in the (Event Pricing) Item drop-down list in the Pricing tab.

4870 (NS:80697): Event Type names are required to be unique.

4776 (NS:79832): (Internet Explorer ONLY) Event attendance number now displays correctly.

4824/4849 (NS:80256/80717): You can now cancel the following Events or Appointments that have been configured with with unlimited units:

  1. Zero dollar (free) Appointments or Events.
  2. Prepaid Activities for which you have booked more than one Appointment or Event Instance using that same activity item.

4848 (NS:80805): The drag-and-drop feature when moving an Appointment now works properly.

4898: The performance issue (speed) for retrieving Event Registrants has been rectified.

4903: Events or Appointments within a cancelled or suspended Agreement can no longer be redeemed. They will no longer display on the list of available prepaid Activities.

4909: The Add Registration window (Events) now refreshes properly if the previous registrant used a prepaid Activity,

<p>4895 (NS:80023): When adding Availability for a Service Provider, the Service Types now display according to ALL of the Service Provider's Work Roles, not just their default Work Role.

For example, if Employee X had both Manager and Personal Training Work Roles, only the Service Types linked to his Manager Work Role (default) would display when setting availability. Now the Service Types for BOTH of Employee X's Work Roles will display.

4915: Event or Service Items (Appointments) configured with Unlimited Units can now be redeemed in perpetuity in Scheduler.

4930/4931: You can now a single Service Provider's availability in Scheduler, provided that their availability has been configured, without an error.

4911: The error when manually selecting an Activity start time in which the Service Provider is available but the Resource is not, has been corrected. You will no longer have the option book an appointment unless the complete time slot for that service is available.

Item Setup

4878 (NS:79885): The scroll bar no longer disables when adding a new item.

Members & Children

4781: Member Cards can now include non-alphanumeric characters ("#" ONLY).

4893/4940 (NS:78385): An error message is no longer thrown when changing the "% of responsibility" and/or the Funding Source on an Agreement from imported data.

4896 (NS:79495): You can now cancel an Agreement that includes BOTH of the following elements:

  1. Includes both paid-in=full and installment options.
  2. The Key Item has expired but there are still associated payment requests.

4873 (NS:80464): The error messages when Updating members has been rectified.

4774: The Allergies and Special Needs tabs now refresh immediately when selecting another child in the Profile.

4786: Children now use their own pool of RoleID numbers and no longer share those with Vendors.

4847: The Member Status now updates with just one click of the Update button when an Agreement has been cancelled.

Member Configuration

4935 (NS:78385): The entries in all fields must be unique on the following configuration pages:

  • Manage Note Types
  • Manage Contact Types
  • Postal Address Types
  • Postal Address Purposes
  • Phone Number Types
  • Phone Number Purposes
  • Email Address Types
  • Email Address Purposes

MosoPay

4864 (NS:80554): The proper information auto-populates the Member Agreement Update window (MosoPay screen) when editing a Funding Source in the Agreements tab.

4889,4883: The Description field on the Edit Credit Card window displays for external Funding Sources ONLY.

Moso myClub

4887 (NS:79183): Event and Service payments are now using the proper Merchant Account Codes and allocating them to the proper Business Unit.

4862 (NS:80203): You can now enter an email address with any combination of characters (all caps, all lower case, or a combination of both lower and upper case) when creating an Account.

My Planner

4742 (NS:79329): A User with all of the proper permissions (Work Role and Operations Security) can delete a task or opportunity without an error being thrown.

POS

4820 (NS:80265): The Member Required flag in Item Setup is now being honored properly during all POS transactions.

4929 (NS:81258): The unknown error message has been rectified when applying a Discount to a transaction.

Template Configuration

4897 (NS:79267): The ${LocationAddress1} Template Configuration code will now render the correct appointment/reservation Location in the appointment confirmation email.

Technical Information

This section list changes to MosoMRM API protocols and Moso myClub Event parameters and deep linking.

In order to keep MosoMRM strictly PCI compliant, we will only be dealing with tokenized data within this new MosoMRM API.

Moso myClub Event Page Parameters

Starting with the MosoMRM 1.85 release, Moso myClub allows the use of various parameters within the URL of the Events module. The table below describes each available parameter. (IMPORTANT REMINDER...Parameter names are case sensitive.)

Moso myClub Event Page Parameters
Name Description Example Usage
date Determines the week of events to display. The week will always start on a Monday and end on Sunday with the specified date being equal to or contained within the start & end of the week. If blank or not used, the current day will be set by default. On a mobile phone, the display will be only for a single day as specified by this parameter rather than the full week.  ?date=12/31/2013
filterLabel The text that appears above the user-selectable event filters. If not used, “Filter” will be the default.  ?filterLabel=Select%20One
locations A comma delimited list of Business Unit Codes as defined in MosoMRM that will be the only choices available to the user in the “Location” filter. If not used, then all locations with schedulable events as defined in Moso MRM will be available.  ?locations=Loc01,Loc02,Loc03
locationCode A single Business Unit Code as defined in Moso MRM that will be the default location selection when viewing the Events page. ?locationCode=Loc01
categories A comma delimited list of Event Category Ids as defined in MosoMRM that will be the only choices available to the user in the “Types” filter. If not used, then all categories with schedulable events as defined in MosoMRM will be available. You can use the “GetCalendarEventCategories” Moso myClub API to get a list of categories and their associated Ids.  ?categories=1,2,3
categoryId A single Category Id as defined in MosoMRM that will be the default category selection when viewing the Events page. You can use the “GetCalendarEventCategories” Moso myClub API to get a list of categories and their associated Ids.  ?categoryId=1
employees A comma delimited list of Employee Ids as defined in MosoMRM that will be the only choices available to the user in the “Who” filter. If not used, then all employees with schedulable events as defined in Moso MRM will be available.  ?employees=1,2,3
employeeId A single Employee Id as defined in MosoMRM that will be the default employee selection when viewing the Events page.  ?employeeId=1
allowLocationChange Determines if the user can select a Location to filter by. Valid values are: yes/no. If “no”, the selector will not be visible to the user, otherwise it will be visible.  ?allowLocationChange=no
allowEmployeeChange Determines if the user can select an Employee to filter by. Valid values are: yes/no. If “no”, the selector will not be visible to the user, otherwise it will be visible.  ?allowEmployeeChange=no
allowCategoryChange Determines if the user can select a Category to filter by. Valid values are: yes/no. If “no”, the selector will not be visible to the user, otherwise it will be visible.  ?allowCategoryChange=no
allowDateChange Determines if the user can select a Date. Valid values are: yes/no. If “no”, the selector will not be visible to the user, otherwise it will be visible.  ?allowDateChange=no

Each parameter is independent with no dependencies on any other parameter and multiple parameters can be specified on the same page. Hence, you may inadvertently configure the Events page to have a non-sensical combination of filters and default values so please be careful when using these parameters.

Moso myClub Event Page Deep Linking

Starting with the MosoMRM 1.85 release, Moso myClub allows deep linking into the workflow of the Events module. The following scenarios are currently supported:

Direct Registration of a Single Event:

In this scenario, the calendar of events is most likely served from a different server and site than Moso myClub. When you select an Event from the externally hosted calendar, you will be directed to Moso myClub in order to complete the booking process. In order to accomplish this, you will be redirected to the Moso myClub Events page using the following URL:

[YOUR_MYCLUB_URL]/#event/date/{eventDateId}/occurence/{eventOccurenceId}

In the URL above the two (2)variables {eventDateId} and {eventOccurenceId} must be supplied. These variables are specific to each bookable event and can be obtained using the “GetCalendarEventSpan” Moso myClub API.

When successfully implemented, you will land on the Moso myClub Events page and instead of seeing the normal calendar view, you will be presented with the details of the specified event and be able to continue the workflow by booking the event.

MOSOPay API - Tokenize Charge Account

You can tokenize a raw charge account number that can be used when calling other MosoMRM APIs. This changes the existing MosoPay encrypt API in the following ways:

  • Adds an "AccessControl" database table with the following columns: [Tenant] (varchar), [ApiKey] (guid), [PublicKey] (binary).
  • Add the following input parameters to the encrypt API controller: tenant=x&apiKey=y
  • Validate the tenant & apiKey parameters against the values stored in the table, reject the request if they do not match.

MOSOPay API - Detokenize Charge Account

You can retrieve the original charge account numbers that have already been tokenized. This adds a new API endpoint to MosoPay.

  • Each request will be composed of the following parameters:
    • ChargeAccountToken
    • Tenant
    • ApiKey
  • The incoming request will validate the Tenant and ApiKeys against the values stored in the AccessControl table and reject the request if the values do not match.
  • The incoming request will validate the ChargeAccountToken parameter using the MosoPay Real-Time HTTPs Integration Token Structure.
  • If the requests validate, MosoMRM will issue an unencrypt request against strongauth.
  • The unencrypted value will only reside in memory and will never written to disk.
  • The unencrypted value will then be encrypted using RSA PGP (or compatible GPG) against the matching PublicKey value in the AccessControl table and returned as the result of the successful API call.

Funding Source API - Add New Funding Source

You can add Funding Sources to client Accounts in MosoMRM via the API.

  • Add ClientAccountPaySourcesPost endpoint with this route: [POST] /api/1.0/clientaccounts/{ClientAccountId}/paysources/
  • The input parameters should be a ClientAccountPaySource entity. As an alternative, you can decide to trim down this entity to only the relevant input data required.
  • The ClientAccountPaySource.ChargeAccountToken property should validate against the MosoPay Real-Time HTTPs Integration Token Structure.

Moso API - Update Existing Funding Source

You can modify existing Funding Sources attached to customer accounts in MosoMRM via the API.

  • Add ClientAccountPaySourcesPut endpoint with this route: [PUT] /api/1.0/clientaccounts/{ClientAccountId}/paysources/
  • The input parameter should be a ClientAccountPaySource entity. As an alternative, you may decide to trim down this entity to only the relevant input data required.
  • The ClientAccountPaySource.ChargeAccountToken property should validate against the MosoPay Real-Time HTTPs Integration Token Structure.

Previous Releases

MosoMRM 1.00 | MosoMRM 1.01 | MosoMRM 1.02 | MosoMRM 1.02.5 | MosoMRM 1.30 | MosoMRM 1.31 |MosoMRM 1.40 | MosoMRM 1.41 | MosoMRM 1.42 | MosoMRM 1.50 | MosoMRM 1.51 | MosoMRM 1.52 | MosoMRM 1.53 | MosoMRM 1.60 | MosoMRM 1.70 | MosoMRM 1.80 | MosoMRM 1.85 | MosoMRM 1.86 | MosoMRM 1.87 | MosoMRM 1.90 | MosoMRM 1.91 | MosoMRM 1.95 | MosoMRM 1.95.1 | MosoMRM 1.95.2 | MosoMRM 1.95.3 | MosoMRM 1.95.4 | MosoMRM 1.96 |

The MosoMRM Modules

My Planner
Members
Check-In
Childcare
Point of Sale
Activity Management
Staff & Users
Data Analytics


System Configuration
Scheduler
Events
Organizations
Time Entry
Time Records
BOSS


System Configuration
The MosoMRM User Interface
The MosoMRM Glossary
Setting Up Your MosoMRM System
The MosoMRM Modules
Operation Security
Feature Security
Moso myClub