so if my customer has a custom Sales Order Approva...
# sdfe
erictgrubaugh
04/08/2019, 10:42 PMso if my customer has a custom Sales Order Approval process, a custom Project Creation process, and a big fancy custom UI for purchasing, then I'd have a
sales-order-approvalproject-creationbig-fancy-custom-uiđź‘Ť 1
m
Mariano Saenz (NS Eng Lead)
04/09/2019, 12:06 AMThat’s a good way of organizing it. I am curious, what do you do in circumstances where a script or object is used heavily in multiple “features”?
e
erictgrubaugh
04/09/2019, 3:18 AM@Mariano Saenz (NS Eng Lead) No hard and fast rule for that. If it is used in multiple unrelated features, and it's the only thing like that, it might get its own project that gets added as a dependency for the other projects
erictgrubaugh
04/09/2019, 3:19 AMIf there are many common objects/scripts like that, I'll make a project I refer to as
Core Utilitieserictgrubaugh
04/09/2019, 3:19 AMI can't say I've come across that use case very often
m
Mariano Saenz (NS Eng Lead)
04/09/2019, 3:40 AMMakes sense. That's what I suggest to do as well. You should stay away from having files and objects in more than one living project, or you are bound to run into problems. It may be useful to give you a way to associate a file and object with a project so as to disallow accidental updates to them by other projects. Something like a project ID. Similar to what we do with SuiteApp project types.
e
erictgrubaugh
04/09/2019, 3:50 AMYes that would be helpful; if I'm understanding correctly that same ID could be used to define dependencies between Customization projects, not just SuiteApp projects
đź‘Ť 1
m
Mariano Saenz (NS Eng Lead)
04/09/2019, 6:02 AMCorrect
s
stalbert
04/09/2019, 7:17 PMsounds useful