New "Date Submitted" and "Last Updated" Columns Added to Form Exports
To provide clients more descriptive and nuanced date/time stamps for their form exports - Events, Donations and Membership Campaigns, and Commerce Forms - two new date stamps have been added. These new date stamps will provide a much clearer picture for analyzing form submissions and transactions. NOTE: This does not apply to standard forms, but if your standard, non-commerce form has an instance field, then the columns will be populated in the online export.
These new date/time stamps appear in the exports contiguous to the existing date_added column.
Date Submitted (date_submitted) - This is the date/time stamp for when the user completed the form submission, whether by final submission of the form or by successfully completing the commerce transaction. This Date Submitted will not change through the life of the particular form submission.
Last Updated (last_updated) - This is the date/stamp of the original date of the submission, but which then changes to reflect the date/time of any subsequent edits or adjustments by the registrant or an admin
Due to the current profile form system functionality for generating last updated values on a per field basis for update fields exports, these columns have not been added to Profile Form exports. This will be done in a future enhancement.
NOTE: Clients who have an automated offline process that depends on specific defined column headers and/or order will need to update the process to include these new columns. This does not affect the current web services query filters for start and end dates.
Event Reporting Enhancements
In addition to the new Date Submitted and Last date-stamps that will be available in Event Exports, there are two more event export enhancements requested by clients in this release.
1. Reworking of "Guest of" Column - Because there was no value for "Guest of" for the registrant themselves, clients have not been able to sort their exports by registrant groups. This has been addressed by reworking the "Guest of" to change it to be "Registered By" and include the name of the registrant in their respective row. With this enhancement clients will now be able to easily sort and group parties together in their event exports. NOTE: This enhancement applies to Custom Exports as well as the Submissions grid. This enhancement is not available on "Canned" reports, such as the Registrant Report or on the Attendee List.
2. Add additional fields to a Category Specific or Activity Specific exports - To provide clients more flexibility for building exports for specific categories or activities, the system has been modified to allow other fields from the same event or any profile form field to be added to those exports. Clients will now be able to build exports for a specific activity, or for a specific category in the event, and be able to add additional information on the registrant from other data fields collected in the event and from the registrants' member profile records.
This new enhancement will support saved field lists that contain fields from the same event or from the profile form.
Web Services Enhancements
There are two new enhancements to the iModules Web Services API:
1. New "is_reviewed" Override - Is_reviewed is the iModules API marker that says if a user transaction has completed the Non-member merge and Identity Checkpoint process or not. Certain clients using partner middleware seek to utilize Identity Checkpoint and the non-member merge systems in their iModules installs, but still want to be able to pull transactions from iModules on a real time basis, regardless of whether the "is_reviewed" flag has been set by the completion of those processes.
Clients utilizing middleware, primarily the Ellucian Connector, to retrieve transactions from the API needed a way to utilize the Non-member merge and Identity Checkpoint, but at the same time want to be able to pull transaction record from iModules without waiting for these processes to complete. The Ellucian Connector is based on pulling only Is_reviewed = true transactions. As a result the transaction pulls will not get a transaction until it has completed the ICP and.or the non-member merge process. This is in contrast to the reports from their payment gateways which show transactions on a real time basis, thereby making end of the day reconciliation very difficult.
Now, iModules personnel will can enable this setting for a client which will mean that all transactions will be returned in a given time period, whether reviewed or is_unreviewed, purely based on the purchase date and ignorning the is_unreviewed request on the middleware call.
2. Commerce Item Price Label Added to Transaction Info - To make it easier for clients using the iModules API to distinguish various items purchased, a price label has been added to the transaction query that will have the name of the item purchased.