Sign Up Use Case

Steps¶

Go to https://arda.cards or other promotional link.
Click on Sign-up
Enter minimal information (e.g. email, Name, Phone)
Show a Splash page with the features of the Freemium plan (in the future this will allow choosing plans).
If User Confirmation (not for first implementation)
1. System sends an email to user to confirm sign-up.
2. User clicks on confirmation link in the email and goes back to the system.
System shows T&C for use of Arda systems.
Accept T&C of use. User can open another window with T&C and print from there if needed.
Input information needed to be able to create the “minimum” model (See Work in progress => Sample Configurations)
Submit, System Validates (edit if corrections needed) and creates Tenant Configuration
User is sent to Application Landing Page.

Scenario¶

Notes¶

The Signup Confirmation Lambda is used to auto-confirm the user in Cognito. This is temporary until the system is running, and the confirmation process is fully implemented (and agreed with business stakeholders).
The Post Confirmation Lambda is used to create the initial tenant configuration and user profile in the Arda system when a new user is confirmed. This can be replaced by a direct call from the BFF to the Arda API Endpoint.
If the profile information includes a tenant identifier or “joining key”, the system will retrieve the tenant and assign the user to it. Otherwise, the system will create a new tenant and its initial Organization Configuration.

Scenario Detail: Create Initial Operations Configuration¶

This sub-scenario shows how to build the initial operations configuration for a new tenant as shown in the section below.

Minimal Organization and Facility Configuration¶

Alternate Minimal Tenant/Facility Configuration¶

This is a slightly more complex configuration that includes an internal station to represent all internal
operations in the facility and two Kanban loops (one for inbound and another for outbound). This configuration
would allow for more detailed tracking of consumption of raw materials and availability of finished goods.

Dashboard Page Notes¶

The dashboard page for a user should act as a control panel to give easy access to the systems features and key information on the status of the Organization’s operations. Possible information and controls to include:

Organization Name with link to edit organization details.
User Name with link to edit user profile.
Number of Active Cards by State: A table with rows for each defined card state with the number of cards in each state.
Top Items: A small table with the top 5 items in the system by number of cards active.
1. Link to the Items Management page to add, edit or remove items.
Links to key operations (key use cases)

Note that these are potential sections in the dashboard page, further discussion is needed.