Request clarification before answering.
Hi Rodrigo,
you can also just do the following:
1. Create 3 extension fields in XBO
2. Create a new "Embedded Component"
3. Bind in "Data Model" the root node to the standard BO (the XBO that you enhanced)
4. Add a new data field and bind it to the InternalID of the standard BO
5. Create 3 data fields in the data model and bind them to your extension fields of the standard BO
6. Add an unbound data field to the data model "EC_ID_IN"
7. Create an Inport in Controller and link the parameter to "EC_ID_IN"
8. Add one Event-Handler "BO-Operation" Read that reads based on the "Alternative Key" and has the EC_ID_IN and the InternalID of the standard BO in the pathes.
9. Drag and Drop the bound extension fields from the data model to the Designer Tab and make them as "TextAreas"
10. Bind your EC in standard UI using the alternative key as a binding for the public outport
btw: LANGUAGEINDEPENDET_EXTENDED_Text is not limited to 255 chars in XBO's...
I cannot post pictures right now to explain it a little better but it should definetly work that way and it is relatively simple without involvment of any partner BO. Just 3 extension fields, one EC and some bindings...
Cheers,
Jens
Update: Screenshots showing the EC configuration:
Update2: I used the Internal ID, you can also use the UUID, this depends also on the Anchort that is available in the standard screen on the public outport.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.