Вернуться   AXForum > Microsoft Dynamics CRM > Dynamics CRM: Blogs
Забыли пароль?
Зарегистрироваться Правила Справка Пользователи Сообщения за день Поиск Все разделы прочитаны

Опции темы Поиск в этой теме Опции просмотра
Старый 12.02.2018, 04:12   #1  
Blog bot is offline
Blog bot
21,466 / 728 (67) +++++++
Регистрация: 28.10.2006
crmtipoftheday: Tip #1073: The story of the small change

“It’s a small change, we don’t need to test it” said many a CRM administrator. What could go wrong?

Maybe this ancient CRM proverb will make you rethink that idea:

Because the admin added a field to the opportunity form, the field count increased beyond the mobile field count limit,
Because the field count increased beyond the mobile field count limit the form script couldn’t find the “next appointment date” field on the opportunity,
Because the form script couldn’t update the “next appointment date” field, the workflow that creates the appointment didn’t run,
Because the workflow that creates the appointment didn’t run, the sales meeting didn’t synchronize to the sales rep’s calendar,
Because the sales meeting didn’t synchronize to the sales rep’s calendar, the sales rep missed the meeting,
Because the sales rep missed the meeting, she lost the sale,
For the want of a sale, the sales rep was fired,
And all for the want of a proper testing procedure on small configuration changes.

Many variations of this proverb have appeared over the years, such as one where an administrator removes an option from an option set that makes a business rule fail, leading to corporate bankruptcy, or a configurator adding a lookup field to the accout form without granting users security permission to the lookup entity making an approval process not run, causing a nuclear power plant reactor meltdown. Whichever variation you prefer, the lesson is the same:

  • Small changes can have big consequences
  • All changes, no matter how small, need to be properly tested before moving to production
  • There is a correlation between complexity of form scripts and work flows and the amount of testing required for small changes. A form with very few automations will need minimal testing when making changes to it, a form with many complex dependent automations will require extensive testing of modifications.

Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.

Похожие темы
Тема Автор Раздел Ответов Посл. сообщение
crmtipoftheday: Tip #1057: Voice of the Customer says “Don’t change your URL” Blog bot Dynamics CRM: Blogs 0 19.01.2018 06:11
crmtipoftheday: Tip #1026: Change your perspective on tracking email Blog bot Dynamics CRM: Blogs 0 20.11.2017 09:11
stoneridgesoftware: Changes to Microsoft Dynamics NAV Change Log System: How to Revert its Behavior Blog bot NAV: Blogs 0 23.06.2016 20:13
german_nav_developer: Übersicht der Trainingsunterlagen für Dynamics NAV 2013 Blog bot Dynamics CRM: Blogs 0 06.12.2012 15:07
german_nav_developer: “Wutschen und Wedeln”: Sortieren und Filtern in Dynamics NAV - Unterschiede zwischen SQL Server und Native Blog bot Dynamics CRM: Blogs 0 20.05.2011 21:06
Опции темы Поиск в этой теме
Поиск в этой теме:

Расширенный поиск
Опции просмотра

Ваши права в разделе
Вы не можете создавать новые темы
Вы не можете отвечать в темах
Вы не можете прикреплять вложения
Вы не можете редактировать свои сообщения

BB коды Вкл.
Смайлы Вкл.
[IMG] код Вкл.
HTML код Выкл.
Быстрый переход

Часовой пояс GMT +3, время: 15:21.
Powered by vBulletin® v3.8.5. Перевод: zCarot
Контактная информация, Реклама.