Here’s a look at the features covered in the maintenance module.
Multi-factor Authentication (MFA) From February 2022, MFA will be required – there may be some exceptions – for all customers. This is to provide increased user account security in the face of the global threat landscape. The added security outweighs the inconvenience. Salesforce provides an MFA rollout pack.
Interactive Lightning Pages with Dynamic Interactions Increases interactivity of lightning pages. Devs create a component and define the behaviour i.e. the events which are exposed. Admins hook up the component on the Lightning page by creating interactions between the source and target components.
Grant access based on Activated User Sessions for Permission Set Groups Enhances the ability of session-based access control. Previously, this had to be managed at the permission set level but with this enhancement it can be done at the permission set group level. The hands-on activity relates to this feature.
Additional options when debugging a Flow A number of options to manage how Flow debug messages are displayed.
Lightning Page performance analysis Use this tool to get insights on the performance of custom Lightning components. This tool includes suggestions on how to improve performance after it detects possible issues.
Some great new features released. Here are a few of our favourites.
Dynamic Gauge Charts
Dynamically update gauge target performance values with values from the underlying report. Without this feature the target performance value had to be manually updated. Details here.
Control access to sensitive data
Previously some record visibility was exclusively governed by the parent record visibility. For example, a Task or Event’s visibility is based on the related Account’s visibility. If the Account publicly visible so were the child tasks and events.
This update allows for a further level of restrictions to be applied. Details here.
Org-specific performance analysis of lightning page performance
Lightning page performance has been a user bugbear from day 1. This tool gives you Org-specific metrics on page performance during the last 90 days. This highlights the worst and best performing pages. Details here.
Restriction rules enable better visibility control over some objects. For example, tasks and events inherit permissions from the parent object they are related to, such as an Account record. If the Account is publicly visible so will be the child events and tasks. By using restrictions rules visibility can be limited in various ways such as limiting permissions to only the task record owners. Details here.
There is a lot to unpack. Not least of which is all things Flow. Flow is set to be the future for workflow automation and will completely supplant Process Builder at some point.
If an Org has two nodes immediately below the prime node there is an issue with including all records owned by users in these two nodes.
Under the prime node CDV there is a CEO and a Co CEO node.
When defining the scope of records in a report filter the prime node, CDZ, cannot be selected.
A choice has to be made between one or the other CEO node.
This is not a problem in a list view since all opportunities can be selected in the record scope without having to choose a node other than the prime node as is the case for reports.
The workaround is to either use a list view or create the report in Classic where all opportunities can be selected. Note that if you edit the report in Lightning after it has been created in Classic it will assume the above behaviour and the report will be limited to the first CEO node.
Update (4th Nov 2018): This is a known issue and will be fixed in a Winter ’19 patch
1. Pick 3 burning issues to fix / improve or new initiatives to generate value. What is important is having a clear picture of the full vision and selecting a technology stack which will support adding functionality as required.
2. Identify metrics to measure the benefits for e.g. increase conversion of website visitors by x percent, decrease admin time to process sales by x days, etc. Start with a baseline measure even if it is an estimate. Build dashboards and reports which can readily show the improvement in the metrics.
3. Identify one person or team to drive and deliver the implementation. Has the mandate to make decisions or can easily get to decision makers.
When it comes to managing the overall change:
4. Ensure that the leadership team is fully bought-in and understands the impact of the new system on the ways of working (the change will not only be a system change but will require changes to processes and how people work)
5. Make the case for change and ensure that it is commonly understood (the why, what, how, etc) across the organization. Most people would agree that emails and spreadsheets are not the most efficient way to work but changing well-established habits and getting someone to log onto a new system and do a task differently requires change effort. Must have a clear answer to the question ‘What’s in it for me?’
6. Don’t underestimate the need for training and communication. These are just as important as the technology and directly lead to better adoption of the system.
Zoho Creator is a useful and versatile platform. One of the more common requirements, especially when creating a new app, is to import data. While it has a decent import tool there is a limitation worth noting.
Using Numbers on a Mac I was unable to select a Numbers date format which was compatible with the Zoho form date format. The format is dd-MMM-yyyy. This cannot be changed – or I couldn’t easily find where to change this. Numbers does not support this format. As a result I had to use Google sheets.
When measuring adoption it’s useful to see the number of logged in users for a given period as a percentage of the total user base. Since Salesforce reports can only report on what data is visible (as is to be expected) it’s not possible to compare logged in users to total users. There is a way around this by using a joined report.
Create a joined report using User as the primary object. This will create a Users block.
Drag a field from the Users object over to an empty space in the preview area. This will create a second Users block. It’s a good idea to use a field which is required for reporting purposes since the report will be grouped at this level.
Filter the second block on logged-in users for the desired time frame.
Create a cross-block formula field using the Record Count summary fields from each block to divide the number of logged in users from block 2 by the total number of users from block 1. This field will typically be called Logged In Percentage or something similar. Change the formula to field type to percentage.