App (n) /æp/ – data that is modified or approved by a set of human or system behaviors.
Layman’s term: a WORKFLOW + a FORM
Approve (v) /əˈpruːv/ – a positive response to an approval TASK
Layman’s term: “Looks good to me.”
Chaos (n) /ˈkeɪ.ɑːs/ or /kay-haas/ – The usual state of business where no one takes responsibility and no one knows what is going on.
Layman’s term: KiSSFLOW’s archenemy
Clarifications (n) /ˌklær.ɪ.fɪˈkeɪ.ʃən/ – responses to queries submitted by previous users
Layman’s term: “What I meant was…”
dLookup (n) /diː lʊk ʌp/ – to directly find values from a MASTER or another APP
Layman’s term: The Gluon Gun of KiSSFLOW tools
Field (n) /fiːld/ – a portion of a FORM used for capturing a data.
Layman’s term: A part of the form.
Form (n) /fɔːrm/ – the mechanism used to capture the data using FIELDS.
Layman’s term: The things that holds all of your data.
Get Clarity (v) /ɡet ˈkler.ə.t̬i/ – to request additional information on an ITEM before approving
Layman’s term: “Huh?”
Item (n) /ˈaɪ.t̬əm/ – a single instance of an APP
Layman’s term: That thing you sent me last wednesday
Master (n) /ˈmæs.tɚ/ – a set of data that exists independent of a FORM that can be referenced by multiple APPS
Layman’s term: Laymen are not allowed to speak of Masters
Report (n) /rɪˈpɔːrt/ – a set of data run through different parameters to show patterns
Layman’s term: Mark in Accounting’s favorite feature
Task (n) /tæsk/ – an individual portion of the workflow. Can be either an APPROVAL, an INPUT, or a CLARIFICATION.
Layman’s term: What you are supposed to be doing right now.
Workflow (n) /ˈwɜːkfləʊ/ – a set of human and system TASKS. Can be sequential, conditional, or asynchronous.
Layman’s term: The flow of how stuff gets done
< go back >