Kbase P87889: How to extend DynCombo Class when using Roundtable ?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
GOAL:
How to extend DynCombo Class when using Roundtable ?
GOAL:
How to create a new Dynamic Object Type with static template when using Roundtable ?
FACT(s) (Environment):
Roundtable 9.x
Dynamics
OpenEdge 10.0A
FIX:
This solution describes the Roundtable specific steps to follow in order to be able to add a new dynamic Object Type with static template.
For Dynamics specific steps description see: "Extending Object Classes with Progress Dynamics" white paper at www.progress.com.
1. We are going to add and change objects inside Roundtable, so first of all we need to select a Task in Roundtable.
2. Define the new Object Type:
- In Dynamics Development Palette open Object Type Control and search for the class we want to extend - DynCombo in our case.
- Right Click on it and select "Add Object Type".
- Fill-in the object details:
Object type code: MyDynComboClass
Object type description: My Dynamic Combo Smart Field
Class object name: rydynsdfcp
Extends object type: DynCombo
3. Add the link between the new created Object Type in Dynamics and its correspondent in Roundtable:
Note: - the DynCombo template is a static object (.w file) and the future objects will be dynamic. To be able to register the template in Roundtable, MyDynComboClass should temporary point to a static Roundtable Subtype.
So in Object Type Control -> SCM XREF tab add the following record:
SCM tool: Roundtable TSMS
Object type code: MyDynComboClass
SCM object type: StaticSDF
4. Create the template file:
- Open ROM tool (Repository Maintenance)
- Search for Object Type: MyDynComboClass
- Expand MyDynComboClass, Right Mouse Click on the Objects and choose "Add Smart Object "
- fill-in the object details:
Product: your product
Product Module: your product module
Object type code: MyDynComboClass
Object filename: MyDynCombo_template.w
Object .description: My Dynamic Combo template
Layout: None (00)
- Save
5. Edit the template file to add new functionalities.
- The template is a static file (.w). So you can extend the template starting with the dyncombo.w: you can make an OS copy from dynCombo.w to MyDynCombo_template.w, and then open MyDynCombo_template.w in Dynamics and add all the new functionalities you want.
- For adding new object class attributes see: "Extending Object Classes with Progress Dynamics" white paper at www.progress.com.
6. Check In MyDynCombo_template.w in roundtable.
7. All the future Objects in MyDynComboClass will be dynamic. So now that we have added the static object in the MyDynComboClass, we have to change the MyDynComboClass Object Type SCM XREF to point to a Roundtable dynamic (.ado) Subtype.
- In Roundtable -> Admin -> Code Subtypes add a new Code Subtype:
Subtype: MyDynComboClass
- Add the following Subtype part:
Subtype parts: 1
Extension: ado
- In Dynamics open Object Type Control and search for MyDynComboClass
- Go to SCM XREF and change it to:
SCM tool: Roundtable TSMS (RTB)
Object type code: MyDynComboClass
SCM Object Type: N contentEditable=false>MyDynComboClass
8. Add the MyDynComboClass to the AppBuilder Palette (and eventually in AppBuilder) as is described in "Extending Object Classes with Progress Dynamics" white paper, chapter "Adding a Custom Palette Instance".
9. Check in all the objects in current task and complete the task.
Now the MyDynComboClass is ready to be use.
.