XBE pertains to a change request that requires special handling: • such as post-invoicing changes to time cards, shifts, or rates. • This type of request is out-of-process • meaning it varies from the standard procedure, • and hence requires validation.
two ways via the :sombrero: process— • 1) we track and validate dangerous data changes • 2) we make those data changes • We can reduce risk of the dangerous change by validating the request makes sense before the actual change is made.
is the result of something going wrong. • * One of XBE’s goals in processing a ‘Sombrero’ is to make them not happen again. • * When someone has a broken arm, of course you want to fi x it, but maybe also fi nd out the monkey bars aren't safe? • * And sometimes someone comes in with a broken arm and asks for antibiotics. So, when I fi gure out what went wrong, I'm like, oh, you need a cast! • * Or perhaps it's like a doctor's appointment. Sometimes you just want the prescription, but you should know the doctor will ask questions… •
bf4
ryomaru0825
sansantech
shift_evolve
nrinetcom
ymty
kkato1
qa
limes2018
cmhiranofumio
yahonda
nishihira
ryanjones
axbom
raygrieselhuber
garrettdimon
frankvandijk
kimpetersen
chrisshort
csswizardry
sabderemane
cassininazir
michaelherold
![www.x-b-e.com Benjamin Fleischer, 2024-11-14, RubyConf benjamin- fl [email protected] gh: bf4](https://files.speakerdeck.com/presentations/6269d192d7b64866b47955c1ea660c05/slide_12.jpg){kind=link}