Articles on: Codebot for SAP SuccessFactors

CodeBot for SAP SuccessFactors User Manual

Table Of Contents

**Platform & Navigation Review**

Access workbooks by navigating to either a Workspace or a Module window as directed via the nine areas shown below.

CodeBot Logo – Takes you Home.

Profile Dropdown – Reset Password, set preferred time zone.

Home button – Takes you Home.

Workspace – Access the Workspace window. Share, Edit, Delete Workspaces from the Work space window.

Employee Central Dropdown – Access Core Employee Central and EC Configuration UI.

Talent Dropdown – Access Recruiting Management, Onboarding 2.0, PM/GM, Compensation, LMS, and Succession.

Platform Dropdown – Access Employee Profile, Role Based Permission, MDF Picklist, Translations, Import/Export Data, Integration Center, and Migration.

Robotic – Access Robotic Testing

Module Tiles – Same functionality as the dropdowns. Access to each area in CodeBot

Iterations & Workspaces

Iterations: An iteration represents a specific work effort initiated by the user. Within an iteration users access Workbooks and take actions. There are 7 iterations in the example below. Each row is its own iteration. Six specific areas are shown below.

Add New Iteration

Iteration #, Instance Type, Host, Company ID, and Description are all editable via the Pen icon in the Actions Menu

Sheet – Link to Configuration Workbook hosted on Google Sheets

Actions Menu

Status – Status of the Executions.

- “Ready to Go”- Iteration / Workbook is ready for actions/executions.

- “Complete” – executions have completed correctly to the workbook instructions.

- “Error” – Either the entire execution has failed, or finished with errors in configurations.

Breadcrumbs – links showing navigation steps.

Workspaces – Workspaces are collections of iterations. These might be grouped by Quarter, Company, User, Instance, etc.

Three specific workspace items are shown below.

Add New Workspace

Workspaces in tiles. Click in to access iterations within that workspace

Edit, Delete, and Share Workspace. Workspaces can be shared with authorized users in your CodeBot Company

**Actions Menu**

The Actions Menu includes the major actions that a user will take when working with CodeBot.

(In order from left to right)

Edit: edit Iteration #, Instance Type, Host, Company ID, Workspace, and Description via the Pen icon. *Useful when migrating changes between instances

Delete: Delete iteration. Note that the workbook will still exist on Google Drive. This action only deletes the link be-tween the CodeBot platform and Google Drive.

Clone: Clone an iteration. A new window pops open with an additional option to clone the entire workbook. *This is much faster than generating a 2nd workbook from scratch.

Share: Share iterations with team members.

Show Progress: The “i” icon allows you to check the status of an Execution at a deeper level. Here is where you access the Tracking ID Request, the Execution logs, as well as Error details. You will also be able see all previous executions on this iteration.

Hamburger Menu: This setting brings you to the key functionality of CodeBot: Generate Workbook, Start Con-figuration, Start Validation, Workbook Health Check, and Compare Iterations.

**Show Progress**

The Show Progress window is accessible via the “i” icon. This window is specific to one iteration. The iteration information (including the Action Menu) is accessible from this window. The main purpose of the Show Progress window is to track CodeBot’s progress as it runs through the execution. This is helpful when troubleshooting.

Action Type and Execution Notes

SAP SuccessFactors Username used to run the execution

Status - Status of the Executions.

(a). “Ready to Go”- Iteration / Workbook is ready for actions/executions.

(b). “Complete” – executions have completed correctly to the workbook instructions.

(c). “Error” – Either the entire execution has failed, or finished with errors in configurations.

Executed by – CodeBot user logged in to run the executions.

Execution time – Once complete, shows how long the execution took to run.

Tracking ID Request – Useful when creating a support ticket. Please copy/paste. the Tracking ID Request in an email to the CodeBot support team for
assistance troubleshooting.

Export, Refresh, and Carrot

(a). Export – Download the log reports to a .csv file.

(b). Refresh – Get the latest updates from the log reports.

(c). Carrot – Open and close log reports. (Close to view more of the previous executions on this iteration).

Log Reports – Detailed report about CodeBot’s progress through the execution.

Screenshots – Screenshots are often available for completed configuration tasks and errors.

**Hamburger Menu**

The hamburger menu includes most of the core functionality performed by CodeBot users

Request Reprocess: When the Status of an iteration is “Complete” and the user selects the hamburger menu, the only option displayed is “Request Reprocess.” Clicking on Request Reprocess doesn’t make any changes to the Workbook or the Instance, it merely refreshes the Iteration in CodeBot so that further actions can be taken.

Generate Workbook: Generates a configuration workbook directly from the instance. This execution is amongst the longest in terms of execution times often taking 1-6 hours to complete, depending on module and volume of configuration information. Regularly performing this action is the best way to ensure up-to-date documentation of your instance(s).

Start Configuration: Configure changes to an instance directly from the workbook.

Start Validation: Scans specific sections of the Workbook and validates whether or not it matches the instance.
This is useful for version controls and troubleshooting. It is also significantly faster than generating a new workbook.

Workbook Health Check: Workbook health check is the CodeBot taking a subjective look at the configuration, and determining if there will be errors in the instance. This functionality is evolving from consultant feedback. Our roadmap includes the continuous enhancement of this capability.

Compare Iterations: Compares workbooks from two different CodeBot iterations. Select an iteration, and then select a different iteration to compare against. The originally selected iteration/workbook will highlight all matching items in green. Items that do not match show in red.


Our workbooks not only provide documentation for the configuration in your instance, but also revolutionize the configuration and maintenance workflow.

Processing Status: The status of a particular item (or items) in the workbook as it relates to an Action Menu item in the CodeBot iteration.

Passed – a neutral state. The items is no longer waiting for execution.

Failed – the item was unable to be configured successfully from workbook to instance.

Pending – The item is ready for an execution dictated from the Action Menu in CodeBot.

Dividers: Dividers or separators are visual barriers, usually black columns, within the Workbook that separate different categories of information.

Process Status Object ID: When there are dividers that separate the Processing Status from the Configuration Information, there will be a Process status Object ID/Name. This allows you to change the process status for that particular item. This item should be listed in Column B of that same workbook tab.

Process Status Column: Past the dividers, next to the Process Status Object ID, there is a separate column to set the Process Status for Object ID. This column with have the Passed/Pending dropdowns.

**Workbook Types**

No Processing Status

Process Status Per Row

Divider/Named Item/Process Status Column

Divider/Named Item/Segment/Process Status Column

Divider/Process Status Per Column

Updated on: 21/05/2024

Was this article helpful?

Share your feedback


Thank you!