Skip to content

Fixing Component Record formId and formName fields (Part 1) ...#437

Merged
bjrebel merged 2 commits into
productionfrom
staging
May 17, 2026
Merged

Fixing Component Record formId and formName fields (Part 1) ...#437
bjrebel merged 2 commits into
productionfrom
staging

Conversation

@krishmaj
Copy link
Copy Markdown
Collaborator

  • component records have had 'formId' and 'formName' fields from the very start of the APA DB, whereas the same fields in action and workflow records have always been called 'typeFormId' and 'typeFormName'
  • absolutely no reason why these fields should be different depending on entity type ... they mean the same thing, and are assigned in the same way - literally the only difference is the field name
  • new administrator utility function to add 'typeFormId' and 'typeFormName' fields to all component records, with values copied from the existing 'formId' and 'formName' fields respectively
  • new components will now have the 'typeFormId' and 'typeFormName' fields added, in addition to the 'formId' and 'formName' ones
  • changed action and workflow records to pull the type form ID directly from the type form itself, instead of the submitted input ... keeps them consistent with (new) component records, and is more reliable in case the submitted input is malformed

Changes have been tested on Staging.

REMINDER - all 'batch' type component type forms will need to have 'subComponent_formId' changed to 'subComponent_typeFormId' in the interface.

krishmaj and others added 2 commits May 15, 2026 11:49
- component records have had 'formId' and 'formName' fields from the very start of the APA DB, whereas the same fields in action and workflow records have always been called 'typeFormId' and 'typeFormName'
- absolutely no reason why these fields should be different depending on entity type ... they mean the same thing, and are assigned in the same way - literally the only difference is the field name
- new administrator utility function to add 'typeFormId' and 'typeFormName' fields to all component records, with values copied from the existing 'formId' and 'formName' fields respectively
- new components will now have the 'typeFormId' and 'typeFormName' fields added, in addition to the 'formId' and 'formName' ones
- changed action and workflow records to pull the type form ID directly from the type form itself, instead of the submitted input ... keeps them consistent with (new) component records, and is more reliable in case the submitted input is malformed
Fixing Component Record formId and formName fields (Part 1) ...
Copy link
Copy Markdown
Member

@bjrebel bjrebel left a comment

Choose a reason for hiding this comment

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

tested on staging

@bjrebel bjrebel merged commit d29492b into production May 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants