Uploaded image for project: 'ui-data-import'
  1. ui-data-import
  2. UIDATIMP-246

Create FlexibleForm Component

    XMLWordPrintable

    Details

    • Template:
    • Story Points:
      8
    • Development Team:
      Folijet
    • Epic Link:

      Description

      It is required to create a Form component that renders itself according to JSON rendering config defined in UIDATIMP-245:

      • This form should be able to render all controls and control / accordion groups according to the valid JSON config given.
      • It should support translation strings, validation rules and styles (as classes) taken from JSON rendering config, their proper attachment and binding.
      • All the rendering configuration JSONs must be stored on backend endpoint for forms configuration values (MOD-story and URL to be created).
      • All the getters and CRUD mutations should be also configured in JSON rendering config.

      May be better to have Stripes to do this; Taras will talk with John C at some point

        TestRail: Results

          Attachments

            Issue Links

            defines

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIDATIMP-325 Data import settings page's 4rd pane for Match Profiles: Create Match Profiles Form renderer

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-2338 Remaining Job and Match profile refinements

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            has to be done after

            Umbrella - UIDATIMP-245 SPIKE: Define Forms Metadata Structure for Match Profiles

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is blocked by

            Task - A task that needs to be done. UIDATIMP-262 SPIKE: Define Metadata Config for simple form rendering

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Task - A task that needs to be done. UIDATIMP-263 SPIKE: Extend Metadata Config definition with accordion sections and static properties

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Task - A task that needs to be done. UIDATIMP-264 SPIKE: Extend Metadata Config definition with RepeatableFields

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Task - A task that needs to be done. UIDATIMP-265 SPIKE: Extend Metadata Config definition with Reference Tables

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is defined by

            Task - A task that needs to be done. UIDATIMP-242 SPIKE: Define SOW and create development stories for Match Profile Details implementation

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

              Activity

                People

                Assignee:
                Ivan Kryzhanovskyi Ivan Kryzhanovskyi
                Reporter:
                taras_tkachenko Taras Tkachenko
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases