Configuring an enterprise package
Adapting without programming: the ladder of answers to a need, the master data to set up first, configurable business rules and rights (groups, per-model rights, per-record rules).
- 24 cards
- 6 topics
- Free
The outline, topic by topic
Each topic is weighted the way the exam weighs it.
- Concepts
- Questions
- Sort and link
- The numbers
- Scenarios
- Understand
A few cards from the deck
Configuration: what is it?
Show the answer
Fitting the package to the company by setting what the vendor planned to be set, without writing code: taxes, numbering, payment terms, validation steps.
It survives version upgrades and costs far less than a development. So it is the first answer to consider when the standard is not enough as it stands.
Each technician must only see the interventions assigned to them, not their colleagues'. What do you configure?
- A record rule: the assigned technician is the current user
- Removing the read right on interventions from the whole technicians' group
- A separate group per technician, each with its own right on the model
- Hiding the interventions menu from those not responsible for them
Show the answer
A record rule: the assigned technician is the current user
The per-model right covers the whole type of object, not rows. Only the record rule filters the visible rows; hiding a menu does not protect the data.
Faced with a need, you first look whether it is already in the …, then whether it can be set by …, and only then whether a … development is needed.
Show the answer
Faced with a need, you first look whether it is already in the standard, then whether it can be set by configuration, and only then whether a custom development is needed.
You climb the ladder from the cheapest to the most expensive to maintain. The last resort, when a gap remains, is to change the company's process rather than the software.
Gap: what is it?
Show the answer
A company need that the package covers neither as standard nor through configuration, found by comparing the need with what the software can do.
Each gap calls for a decision: a custom development, or a change of process to move closer to the standard. They are what drives up a project's cost and duration.