Manage SAS Support Access to Your Tenant
Prior to this release, SAS support personnel could not access your tenant, which prevented them from providing quick answers that depend on knowing how your tenant or items are configured. SAS Technical Support often requests screenshots of your tenant while investigating support requests. For example, they might ask for configuration details, task names, publish dates, and run dates. The communications sometimes resulted in slower resolution time as details were gathered by SAS Technical Support.
With this release, administrators can enable support access under General Settings => Default Permissions => Access for SAS Support Personnel.
When this option is enabled, SAS support personnel can sign in to a tenant to troubleshoot issues that might occur while you are using SAS Customer Intelligence 360. Access to your tenant is limited to Read-Only permissions. Support access is only temporary, and support users are removed automatically from a tenant after 24 hours.
While SAS support personnel have access to your tenant, you might see the SAS email address of the individual who has access. That user is assigned the Support Viewer role, which is visible on the Users tab in SAS App Central and in SAS Customer Intelligence 360 on the General Settings => Roles page.
This option is disabled by default for existing tenants. However, it is a best practice for you to enable this option so that SAS can reduce resolution times and even investigate customer issues outside usual business hours. This option is enabled by default for new tenants.
(Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, and SAS 360 Engage: Email)
Task and Segment Locking
Starting with this release, a task or segment locks automatically when a user opens that item. This feature prevents simultaneous edits to the same item, avoiding item conflicts and lost changes. Locking is particularly useful for large organizations where multiple users collaborate on the same marketing tactics and customer segments. The task or segment becomes unlocked when it is closed by the user or when the user logs out of SAS Customer Intelligence 360.
Other important notes:
- An item that is locked cannot be edited by another user.
- If a user opens an item that is locked by someone else, a warning is displayed.
- Changes that are made to an item that is locked by another user cannot be saved.
(Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, and SAS 360 Engage: Email)
Merge Tags Are Now Case Insensitive
Starting with this release, merge tags are case insensitive. This feature ensures that all merge tags can be resolved regardless of any inconsistencies that might exist when a user enters different cases while defining a merge tag and referencing it.
For example, conditional merge tags that are used in email content can be added in two ways: You can use the Select Merge Tag option, and then edit it, or you can enter the merge tag directly into the source code. In previous releases, these actions sometimes resulted in merge tags with case differences that led to unresolved merge tags. Now, merge tags with case differences are resolved.
Definition of Last Name in Table Management
Example of Mixed-Case Merge Tag Variations
Mixed-Case Merge Tag Variations Resolved
(Available in SAS 360 Engage: Email)
Customize Payloads in Connector Endpoints
When you configure an endpoint, you can specify a custom payload and also include variables in the outgoing request body that is used to invoke the connector. With this feature, you can fully replace the default request payload with the JSON script of an event in SAS Customer Intelligence 360. You can use the default request payload or replace it with the custom payload that can be formatted and tested.
Use this feature to simplify the integration to external systems and eliminate the need for an intermediate code layer to transform the request body.
(Available in SAS 360 Engage: Digital)
Obtain the Mobile SDK from a Public Repository
The mobile Software Development Kit (SDK) for SAS Customer Intelligence 360 is a supporting library that enables a mobile app developer to add support for event collection and managed content to your native mobile applications (apps). In this release, your mobile app developer can access the mobile SDK from a public repository in the following ways:
- The mobile SDK for iOS is accessible in a public GitHub repository. The repository hosts versioning data and manifest data that enable Swift Package Manager (SPM) to manage your project’s dependency on the SDK framework.
- The mobile SDK for Android is accessible in a privately managed maven repository.
Instructions for mobile app developers are provided in SAS Customer Intelligence 360: Developer’s Guide for Mobile Applications.
The previous method is also supported. That method requires a SAS Customer Intelligence 360 user to download the mobile SDK through the user interface for SAS Customer Intelligence 360 and deliver the SDK ZIP file (SASCollector_<applicationID>.zip) to the mobile app developer to install. A benefit of this method is that the downloaded files are prepopulated for the customer's selected tenant and mobile app ID.
(Available in SAS 360 Engage: Digital)
Decoupling of SAS Customer Intelligence 360 and the Mobile SDK
The provision of a public repository to obtain the mobile SDK prompted an additional change. The mobile SDK is now released independently of a SAS Customer Intelligence 360 release. Previously, changes to the mobile SDK were released on the same schedule as a SAS Customer Intelligence 360 release. Now, changes to the mobile SDK can be released separately.
Note: The mobile app developer should always work with the most recently released SDK version to take advantage of the latest updates. For the latest changes to the mobile SDK, see Mobile SDK Change Log for SAS Customer Intelligence 360.
(Available in SAS 360 Engage: Digital)
Disassociate and Associate Planning Items within Cost-Center Budgeting
If you work with planning items that have cost-center budgets, you can disassociate a planning item and its child items from the marketing hierarchy. In addition, an orphan item with a cost-center budget can be associated with the marketing hierarchy if the selected cost centers in the orphan item are also available for the intended parent planning item.
When you associate items, the system checks that the available funds in the hierarchy are sufficient to support the association of orphan items. For example, if you associate an orphan item with a plan in the hierarchy, the system checks that the available budget of the plan is sufficient to accommodate the campaign budget.
Similarly, when you disassociate items, the system checks that the available funds from the cost-center budgets are sufficient to support the existing items in the hierarchy and the disassociated items that become orphaned. For example, if the available amounts from the cost centers are fully allocated to items in the hierarchy, you cannot disassociate any planning items because no funds are available from the cost-center budgets for any orphan item.
When the automated system check does not support the association or disassociation of items, manual budget adjustment is required.
To disassociate a planning item from the marketing hierarchy:
- On the Relationships tab of the parent planning item, select the item that you want to disassociate:
- Click
to disassociate the item.
To associate a planning item with the hierarchy:
- On the Relationships tab of the intended parent planning item, click the drop-down list and select the orphan item to associate. For example, select a campaign.
A list of one or more non-associated campaigns is displayed. - Select the campaign that you want to associate, and then click OK.
(Available in SAS 360 Plan)
Export Grid Values from Custom Properties to Microsoft Excel
Custom properties enable you to supplement the standard properties of an item (for example, name, description, and type) with more properties that are specifically applicable to your goal or organization. Grids are a type of custom property in which you can enter data in a row-and-column format.
In this release, you can export the data from a grid to a file that can be opened in Microsoft Excel. This feature enables you to quickly review the grid data for an item and use that data for external applications.
To download the grid data for an item, click 
(Available in SAS 360 Engage, SAS 360 Discover, SAS 360 Plan)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.