Is it possible to share datasource definitions, LOVs, Domains and other objects accross applications?

asked 04 Sep '15, 04:38

Jan%20Willem%20Vermeer's gravatar image

Jan Willem V...
1431436
accept rate: 0%


Hi Jan,

The short answer is: There is no built-in support to share Formspider Objects across applications. You can only share PL/SQL code between applications.

The long answer is: We plan to introduce built-in support for reusable Formspider Libraries in a future Formspider version. This feature is on our road map. Until then, you can create your own templates using the new human readable export file syntax in Formspider 1.9. You can extract human readable versions of your Formspider Objects and store them in a file or files. Later you can import these object into other Formspider applications.

For example, if you have domains you want to reuse in your applications, you can create these domains in an application. Export this application. Edit the rest of the application out and leave only the domains in the export file. Later, you can import this file into any Formspider application using the code snippet below:

declare
  v_template_cl clob;
begin
  v_template_cl:=--custom function which returns the correct export file's content
  bdf_etl_api.import(IN_APP_CL=>v_template_cl, 
                    IN_NEWAPPNAME_TX=>null, 
                    IN_NEWDSSCHEMA_TX=>null,
                    IN_APP_ID=>bdf_application_qry.getid('<TargetApplicationName>'), 
                    IN_CREATEMODE_CD=>bdf_constant_etl.etlcreatemissingonly); -- or use bdf_constant_etl.etlcreateorreplace
end;

Moreover, you can add parameters to these export files and populate these parameters before you import the file into an application. Working with these parameters is not really about Formspider though. This is basic file processing.

For example, you can create a Dialog with OK and Cancel buttons in it. You can export the application which contains this Dialog, edit out the rest and have yourself a Dialog template. You can make the dialog name a parameter in the file. Whenever you need a new Dialog object, you can import this file supplying a "dialogName" parameter.

Hope this helps.

Kind Regards,
Yalim

link

answered 04 Sep '15, 08:34

Yalim%20Gerger's gravatar image

Yalim Gerger ♦♦
1.8k5
accept rate: 15%

edited 04 Sep '15, 08:34

Strange... i added an answer but it seems to be lost in space... i try again.

Do i understand it correcly that a FS application can only be executed when every object is valid and present in the application? When i edit the XML i have to enter existing lov's and domains. Otherwise an error will to raised.

So, this export/import solution saves a lot of time copying objects from one application to another. But when i modify an LOV, i have to do that in every application. With so many objects, it will be just a matter of time before they are all different.

What i meant was something like a library with objects.

Kind regards, Jan Willem

link

answered 04 Sep '15, 09:06

Jan%20Willem%20Vermeer's gravatar image

Jan Willem V...
1431436
accept rate: 0%

Hi Jan,

The library is a feature on our road map with a high priority.

Kind Regards, Yalim

(04 Sep '15, 09:24) Yalim Gerger ♦♦
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×67
×30
×4

Asked: 04 Sep '15, 04:38

Seen: 1,330 times

Last updated: 04 Sep '15, 09:24


© Copyright Gerger 2017