Skip to content

Conversation

@ajeety4
Copy link
Contributor

@ajeety4 ajeety4 commented Dec 23, 2025

Product Description

  • Adds four new formats in the case list config section for display properties.
    1. Geo Boundary (requires Address)
    2. Geo Boundary Color (requires Geo Boundary)
    3. Geo Points (requires Address)
    4. Geo Points Colors (requires Geo Points)
  • Adds validation on save to allow only one property to use these new formats.
  • Adds a mechanism to dynamically display these formats based on other formats.
  1. New formats that are dynamically displayed based on columns with other formats.
New.Formats.mp4
  1. Alert error if dependency format is removed
Validation.mp4

Technical Summary

Ticket

Feature Flag

None

Safety Assurance

Safety story

Tested on Local. QA passed

Automated test coverage

JS changes only.

QA Plan

TBA

Rollback instructions

  • This PR can be reverted after deploy with no further considerations

Labels & Review

  • Risk label is set correctly
  • The set of people pinged as reviewers is appropriate for the level of risk of the change

@ajeety4 ajeety4 added Open for review: do not merge A work in progress awaiting QA QA in progress. Do not merge Core Compatibility Changes may impact Mobile and Formplayer product/all-users-all-environments Change impacts all users on all environments labels Dec 23, 2025
@dimagimon dimagimon removed the Core Compatibility Changes may impact Mobile and Formplayer label Dec 23, 2025
@ajeety4 ajeety4 marked this pull request as ready for review December 23, 2025 07:51
} else {
// Restrict Translatable Text usage to Calculated Properties only
menuOptions.splice(-1);
const index = menuOptions.findIndex(f => f.value.includes('translatable-enum'));
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@minhaminha
I noticed this was removing the last element in the array, so I modified it to remove the correct element. Let me know if it looks correct to you.

Copy link
Contributor

@zandre-eng zandre-eng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One nit, but generally looks fine given that this is going through QA.

Copy link
Contributor

@zandre-eng zandre-eng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the change, looks good!

this is done as it is supposed to be used only for mobile app
@calellowitz
Copy link
Contributor

Where is the xml actually generated and do you have an example suite file with the new fields?

@ajeety4
Copy link
Contributor Author

ajeety4 commented Jan 8, 2026

Where is the xml actually generated and do you have an example suite file with the new fields?

(Updated the example code and suite file in this comment) FYI @calellowitz
Assuming you are asking where in the code, the detail section of the xml specfically the columns in Case List/Detail is generated here. The entry point method for suite generation is here.

Attaching the sample suite file with a geo-boundary and geo-boundary-color fields-
suite.xml

Below is the example how one of the field looks like

    <field>
      <header width="0">
        <text/>
      </header>
      <template form="geo_boundary" width="0">
        <text>
          <xpath function="geo_boundary_value"/>
        </text>
      </template>
    </field>

@ajeety4 ajeety4 added QA Passed and removed Open for review: do not merge A work in progress awaiting QA QA in progress. Do not merge labels Jan 15, 2026
@ajeety4 ajeety4 merged commit f91aa4e into master Jan 15, 2026
18 checks passed
@ajeety4 ajeety4 deleted the ay/case-list-config-new-formats branch January 15, 2026 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product/all-users-all-environments Change impacts all users on all environments QA Passed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants