JADE Environment Development Ideas

What's new in the upcoming JADE release?

IMPROVED DEVELOPER EFFICIENCY. ENHANCED SECURITY. SMOOTHER INTEGRATION

The JADE 2022 release meets tomorrow’s business demands.


Start your update to JADE's latest release

Form control copy/extract/import

We are finding that when a new control is added on a form, the entire form schema is brought over, overwriting the controls that were in the desc env. We need a way to be able to copy and paste controls over from one env to another without having to close the controls on the current env (adding only). 

Ideally, it would be nice to have *.ddbx file takes from one env and have a diff against dest env in the Jade Painter and select which controls to copy over (copy control and it's children).  And when you hit the save on the paint, it should create those controls for you.

We have multiple env of code that have different changes being done on one form, but we need to consolidate it at some point. Having this ability makes it easier to do.

 

At the moment, we have to manually create controls on the source and master env with all form changes.

  • Thaban Segaran
  • Jan 10 2020
  • Needs review
  • Attach files
  • BeeJay commented
    14 Jan, 2020 01:04am

    No worries.  Thought it worth mentioning as an interim work-around.  Your suggestion of allowing copy & paste between different Jade environments would be a nice improvement, assuming it gets implemented in a future Jade release.  :-)

  • Thaban Segaran commented
    13 Jan, 2020 01:44pm

    Hi BeeJay, Thanks for the idea. I didn't think of that. I guess that will work as a workaround for now.

  • BeeJay commented
    10 Jan, 2020 10:35pm

    Have you thought about temporarily renaming the form to FormName_Temp before extracting, and then rename it back again.  Then, you can load the extract into the target environment without losing anything.  Then, in the target environment open FormName and FormName_Temp and you can now copy & paste the desired control, including child controls, from FormName_Temp to FormName.  When you're finished, deleted FormName_Temp in the target system.  If you have any event code, you'll still need to copy that across as well before deleting FormName_Temp, but at least it saves you quite a lot of time/effort manually creating the control and its child controls again.