4 ms·

Custom fields makes sense... do you think those are part of making integrating with other apps easier? https://www.enterpriseready.io/features/integrations/ htt

Custom fields makes sense... do you think those are part of making integrating with other apps easier? https://www.enterpriseready.io/features/integrations/ https://www.enterpriseready.io/features/integrations/ As for easy branding, do you think that only applies a "must have" if the application has some sort of end-customer/consumer facing interface (ie Zendesk, Readme.io etc)? Or do you think that is equally important for applications that are used exclusively internally by employees.

deleted 10y ago
[deleted]
duck 10y ago
Not the OP, but I think they meant more inline with what is common in most enterprise CRM and CMS applications. Something like: https://trailhead.salesforce.com/en/data_modeling/creating_custom_objects_fields https://trailhead.salesforce.com/en/data_modeling/creating_c...
NeutronBoy 10y ago
> Custom fields makes sense... do you think those are part of making integrating with other apps easier It's more about being consistent with other processes and applications that an enterprise already has. If your product is about generating reports, they'll want the button to say 'Generate TPS report' rather than 'Generate report'.
radicalbyte 10y ago
It's a plus for internal apps: there's always some "company first" person in the chain who wants to get brownie points by having their logo visible. It's also very easy to implement, so why not? Auditing remains the killer though, if you build it in from the beginning then it can be effectively free because of how it affects your architecture. If not it can become a big maintenance headache.