Jump to content

Talk:Micro Focus Content Manager: Difference between revisions

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Content deleted Content added
SmackBot (talk | contribs)
m Subst: {{unsigned}} (& regularise templates)
Tygrus (talk | contribs)
Line 9: Line 9:


This article was out-of-date with some erroneous information. Updated with new product name, added references. Took out blatant advertising.--[[User:JLRedperson|JLRedperson]] ([[User talk:JLRedperson|talk]]) 18:56, 19 February 2010 (UTC)
This article was out-of-date with some erroneous information. Updated with new product name, added references. Took out blatant advertising.--[[User:JLRedperson|JLRedperson]] ([[User talk:JLRedperson|talk]]) 18:56, 19 February 2010 (UTC)

== Customizing records and programming ==

Does any one have experience with customizing and programming features into a TRIM system ?
What can normal users change and add to the system ? eg. form layout, add fields, add controls ?
Can users add code to the records / templates / events to add complex and dynamic functionality ?
What can't a user or SysAdmin do that requires a 3rd party developer to modify the system ?
What programming language and/or tools can be used to add complex code to the system (similar to above) ?

How hard is it to add 2 new fields per category/tag/attribute? A keyword field is used to update a dropdown (combo) list of terms related to the keyword (label + code). The keyword and code are then saved in the record. Each document/record could have multiple terms selected (using a relational table to allow an unlimited number per document/record). Three tables are used for the terminology/classification system: Terms, TermKey, Keywords. The TermKey table uses the primary key of the Term table and the primary key of the Keyword table to enable the many-to-many link between Terms and Keywords.
--[[User:Tygrus|tygrus]] ([[User talk:Tygrus|talk]]) 05:16, 11 February 2013 (UTC)

Revision as of 05:16, 11 February 2013

WikiProject iconComputing: Software Stub‑class
WikiProject iconThis article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
StubThis article has been rated as Stub-class on Wikipedia's content assessment scale.
???This article has not yet received a rating on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Software.
Note icon
This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the |auto= parameter.

This reads like marketting material to me. Is that really in line with what Wikipedia attempts to provide —Preceding unsigned comment added by 65.57.245.11 (talkcontribs)

This is blatant advertising —Preceding unsigned comment added by Liampaulmurphy (talkcontribs)

Updated content to reflect new name; added numerous citations

This article was out-of-date with some erroneous information. Updated with new product name, added references. Took out blatant advertising.--JLRedperson (talk) 18:56, 19 February 2010 (UTC)[reply]

Customizing records and programming

Does any one have experience with customizing and programming features into a TRIM system ? What can normal users change and add to the system ? eg. form layout, add fields, add controls ? Can users add code to the records / templates / events to add complex and dynamic functionality ? What can't a user or SysAdmin do that requires a 3rd party developer to modify the system ? What programming language and/or tools can be used to add complex code to the system (similar to above) ?

How hard is it to add 2 new fields per category/tag/attribute? A keyword field is used to update a dropdown (combo) list of terms related to the keyword (label + code). The keyword and code are then saved in the record. Each document/record could have multiple terms selected (using a relational table to allow an unlimited number per document/record). Three tables are used for the terminology/classification system: Terms, TermKey, Keywords. The TermKey table uses the primary key of the Term table and the primary key of the Keyword table to enable the many-to-many link between Terms and Keywords. --tygrus (talk) 05:16, 11 February 2013 (UTC)[reply]