how to make a cloud compatible studio customization for enums

Hi,

is there a way to modify the studio view "modification of a field" in order to add some custom properties to the vardefs while being cloud compatible ?

As of now we were using an admin view and the method "array_to_file" to push our custom properties into a dedicated vardef file, But the recent modifications of the function's black list makes us reconsider how we are doing this.

Any ideas ? 

, , , , , , ,

Parents
  • Dear and ,

    we are aware of the custom fields possibilities that will solve this issue.

    But, on the other hand, custom fields are currently not correclty handled in the report section or though Sugar BPM (and I am not sure about how they are handle with external solutions like Sugar Connect, Market etc.).

    This is why we tried to keep the core ENUM field that fits with our expectation for admin settings, edition, reporting etc. But, for graphical purpose, we created a custom module to specify in which color each option must be displayed.

    The result is an additionnal vardef fields with custom properties that should be handled in a proper way through a custom HBS.

    The problem is that, on the cloud, we canno't create "on fly" custom vardefs file, neither use the ext_ properties for that.

    I don't know if I am clear enough but I will glad to answer to all your question in order to find an cloud compatible and upgrade way solution to solve this problem.

    Many thanks,

    Fred

Reply
  • Dear and ,

    we are aware of the custom fields possibilities that will solve this issue.

    But, on the other hand, custom fields are currently not correclty handled in the report section or though Sugar BPM (and I am not sure about how they are handle with external solutions like Sugar Connect, Market etc.).

    This is why we tried to keep the core ENUM field that fits with our expectation for admin settings, edition, reporting etc. But, for graphical purpose, we created a custom module to specify in which color each option must be displayed.

    The result is an additionnal vardef fields with custom properties that should be handled in a proper way through a custom HBS.

    The problem is that, on the cloud, we canno't create "on fly" custom vardefs file, neither use the ext_ properties for that.

    I don't know if I am clear enough but I will glad to answer to all your question in order to find an cloud compatible and upgrade way solution to solve this problem.

    Many thanks,

    Fred

Children
No Data