CONFIG MANAGEMENT

Computing selective configuration changes between tenants.

DEVELOP - COLLABORATE - DELIVER

As a part of customer implementations, project teams develop new functionalities or extend existing functionalities on a tenant in the Development environment. On completion of the development activity, all the relevant configuration changes need to be promoted to another tenant.

o9 Solutions/ Config promotion process

In a typical project, a flow similar to the one represented above is followed by implementation teams for developing configuration and moving it between tenants. Config Management feature will be used for movement of changes between private tenants within the same organization.

In a large organisation this becomes a tedious job to collate information on config changes and our task was to simplify it.

MY ROLE

I worked on this feature as the lead designer at o9 solutions. I laid down the goals, conceptualised flows, created story board , wireframes, visual designs, and communicated the interactions to developers. By collaborating with our UX team & project manager carried out the user research.

DISCOVERY

Users request,

“ I want to make changes to config on private Development tenant, unit test them, review them iteratively with focus on achieving the end solution without worrying about keeping a track of changes”

“I want to clearly understand what model currently exists in the tenant, with a convenient exploration workflow”

“Be able to receive a change log of all changes moving to the production”

GOALS

1. Thoughtfully designed experience that aims to create a consistent platform for all users, accessible with a framework for rapid development.
2. A shared design model that streamlines establishment and delivery of foundational portal capabilities, and lets the regions focus on higher-level objectives.

USER RESEARCH

* User persona

* User persona

USER ACTION MAPS

*User flow

1. Make config changes on Source tenant

• Entity A was changed to A’
• Entity A was changed to A’

2. Browse and identify config changes using Config Audit

• Change A → A’ was identified and entity A’ was selected

3. Create a Config management (CM) package

4. Import CM package on Target tenant

• Entity A gets changed to A’

LOW-FI WIREFARMES

* Work Flow

MOCKUPS

Config Audit with 3 tabs :

• Summary : Summary of changes — select, create package and publish.
• Details : detailed version of all the changes made in a tenant.
• Milestone : creating checkpoint/milestone, restoring the selected checkpoint/milestone version, selecting checkpoints and comparing the changes .

Summary of changes & apply filters

Quick deletion of filters & Details page

Milestones

Creat - create a new checkpoint

Get Latest - get latest changes from the source tenant

Compare - select checkpoints and compare changes

Create a Config Management package & Publish

Config Management package is now available is organisation’s library : and users can review changes and import packages

INDEX

*Tenant - instance of the software and supporting infrastructure serve a customer.

*Delta - A change/variables

*Checkpoint

REFLECTION

Really listening to users is the key. Discovery of features is one of the most important things to be considered while adding an enhancement .

Thank you for reading

PS : User testing - coming soon!