Introducing
Your new presentation assistant.
Refine, enhance, and tailor your content, source relevant images, and edit visuals quicker than ever before.
Trending searches
What things must we be doing to avoid some issues?
Clients must be hands-on with a their instances as soon as possible. Iteration reviews encourage that with testing of their configuration.
It helps them build an experience with the application, how it behaves and generates questions they may not think to ask any other way.
Role Based Permissions require some systems thinking. Plan beyond your moduel, interact with the other consultants on your projects.
Even among the most experienced consultants, we see a lot and have done a lot, but have not done it all.
We should be demonstrating reporting/dashboardsand gathering reporting requirements during the first iteration to ensure we are accounting for them
Plan for tasks that must be done by SF early in case there is a delay. Hint: There is ALWAYS a delay
The standard company ID is assigned by SF automatically and intended to be changed by the first SI.
Doing it later causes changes in SSO and data loss in JAM
Founded in 2003
Pioneer in cloud-based HCM
Acquired by SAP in 2011
Full-suite solutions
Implemented over 10,000 times
Leading cause of project failures: Consulting issues
Giving up is never an option in the face of an issue. How we address the issue will often help us understand if this is big or small.
When things go wrong, it may be related to changes in the quarterly releases. Stay up to date.
HINT: 1508 IRRs have already begun!
It's important to get your clients to take responsibility early, but manage their permissions carefully, separate responsibilities and touch-base frequently to ensure it is a collaborative arrangement.
many issues can be inspired by a bad admin
Load the standard competency library into every instance and do not alter. Leverage content by creating other libraries with the modified content.
When functionality is not working, the standard library can be used to help find issues including language alignment
Substituting labels in text replacement and 3rd tier language updates can sometimes impact other modules an unintended places.
Set expectations that a change may have those impacts. We cannot alter that outcome
Review at least quarterly for changes in functionality, such as rules. Look for evolving that cover more cases. Not all may have been covered in the IRR
What other issues are originating from requirements?
Copying and pasting from Microsoft Word into XML has one primary hazard. Anything with a single quote, double quote or a dash is likely to cause an error.
Look for parsing errors and some odd messages when loading templates
Starting with a working model and making small changes is the best approach
Keep a revision history of templates to backtrack when things go wrong