Our Clients need to be able to define Actions. We capture so many Events that if we just showed them all, the majority won't be useful.
Requirements
- An Action is made up of one or more Steps.
- A Step contains an Event.
- Steps can contain conditional logic (this Event OR this Event = a Step)
- Use the URL: /Actions/Configuration
UX
We are going to use the same components for the right hand sidebar (the one used to map the Events to a Step). Since that also allows stringing together Steps into an Event.
The difference between the sidebar and the application, is that it's not possible to tag an Event as a Step in the application (it's necessary to go to our Client's app to do this with the sidebar).
In the application, it's necessary for a Client to be able to create an Action from existing Steps. The Client also needs to be able to create a new Step - which will link them to their own app's homepage, but with our sidebar opened.
(This also means, when a new Client is created, we need them to give their app's URL)
Our Clients need to be able to define Actions. We capture so many Events that if we just showed them all, the majority won't be useful.
Requirements
UX
We are going to use the same components for the right hand sidebar (the one used to map the Events to a Step). Since that also allows stringing together Steps into an Event.
The difference between the sidebar and the application, is that it's not possible to tag an Event as a Step in the application (it's necessary to go to our Client's app to do this with the sidebar).
In the application, it's necessary for a Client to be able to create an Action from existing Steps. The Client also needs to be able to create a new Step - which will link them to their own app's homepage, but with our sidebar opened.
(This also means, when a new Client is created, we need them to give their app's URL)