Enforcing required fields from metetagger
Options
From metatagger we would like to prevent the client from saving if the pre-fills didn’t get a value from the DCR. i.e. the Title filed has the required attribute set to ‘t’; however if title is null and the DCR doesn’t contain a value for title, metatagger does not care even though it’s set to required =‘t’
We would like to add this functionality to metatagger so that once the user clicks the SAVE button all the fields are evaluated for required =’t’ regardless if they are pre-fills or not.
Where can we add this functionality in metatagger.
Thanks
We would like to add this functionality to metatagger so that once the user clicks the SAVE button all the fields are evaluated for required =’t’ regardless if they are pre-fills or not.
Where can we add this functionality in metatagger.
Thanks
0
Comments
-
I know this is an old post - MetaTagger supports required fields, so something must be wrong in your datacapture.cfg, because that's where that's controlled.0
Categories
- All Categories
- 109 Developer Announcements
- 49 Articles
- 101 General Questions
- 123 IM Services
- 40 OpenText Hackathon
- 31 Developer Tools
- 20.6K Analytics
- 4.1K AppWorks
- 8.9K Extended ECM
- 897 Cloud Fax and Notifications
- 77 Digital Asset Management
- 9.3K Documentum
- 29 eDOCS
- 123 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
TeamSite Developer Resources
If you are interested in gaining full access to the content, you can register for a My Support account here.
- Docker Automation
- LiveSite Content Services (LSCS) REST API
- Single Page Application (SPA) Modules
- TeamSite Add-ons
If you are interested in gaining full access to the content, you can register for a My Support account here.