Process Builder - Database Write

Hello,

I'm creating a workflow that requires that I connect to an external database. Although I am not having any issues connecting to the database in the configuration of the Database Write activity, I am wondering if its possible to "dynamically" configure the connection string, username and password in the activity.

The issue that I have is that I do not want to have to configure the user / pass in the activity itself as when I change from one envirnment to another I may need to connect using a different user / pass. Is it possible to configure the user / pass for a database write acivity somewhere else that may be more global, instead of in the process itself, so that I do not have to make changes to all of the database write activity that I have in my processes.

Thanks,

Find more posts tagged with

Comments

Miller-zzMST

Hello Roger,

I think you need to develop your custom java method which will call a standard one and pass to it mapped process variables.

~ Konstantin

Roger.Shih

Konstantin,

Thanks for your reply, however I'm afriad that I do not quite understand what you are suggesting. Are you saying that I will not be able to use the default Process Builder's Database Write activity, but instead create my own java method that will do the database writes for me?

I'm not sure how a process variable can be used in the configuration of the database write connection settings. In the configuration screen it does not give me the ability to select a process variable.

Please let me know if my questing is not clear.

Thanks,

Roger

lastnitescurry

Use Registered tables. And use a DQL write activity. Use INSERT DQL statement.

Registered tables have been in Documentum for a long time and should be well know to admins. A big plus is they can be set up and veified to work outside of the business process

https://community.emc.com/thread/119403

from RTFM.... Content Server Fundamentals 6.6

What registered tables are
Registered tables are RDBMS tables that are not part of the repository but are known to Content
Server. They are created by the DQL REGISTER statement and automatically linked to the System
cabinet in the repository. They are represented in the repository by objects of type dm_registered.
After an RDBMS table is registered with the server, you can use DQL statements to query the
information in the table or to add information to the table.
For more information
• The Content Server DQL Reference Manual has information about:
— The REGISTER statement
— Querying registered tables

Miller-zzMST

Roger,

I mean that you can create your custom java method which will call a standard Process Builder's Database Write activity with your parameters.

But gangadhara in https://community.emc.com/message/540189 suggested another solution. It seems to me this method can be a bit improved and you will not need to write any code. But you must understand that Vendor may not support this method and it is possible that in future versions could change something in this area.

So I suggest:

- create any Database Write activity and fillout it with all parameters and make all input and output data mappings:

- export it locally and learn it structure;

- in Forms Builder create an e-form with same structure, it will look like this (place a Table control, group Parameter must be set as repeatable):

- come back in Process Builder and create a few activities before Database Write activity:

- create a package with 'Activity' type;

- at first step you will need to get an object id of that Database Write activity, in my process this is Process Data Mapping where I have a hard binded value;

- next you will need to write a new value for user name parameter (in my case this is hard binded value). User name is stored in third parameter (its name is USERNAME_CONFIG_PARAM). To do this you will need to add an xml schema to package. As xml xsd use the e-form, created on the previous step. If you will need some help how to do this, please ask.

- the last step is our Database Write Activity for which we changed an input parameter (in my case I have the same passwords for users, so its works fine)

Of course, it is necessary to add at the beginning of the process a step, which will analyze the environment in which started the current process and only after that to change something in activities.

As alternative, you can create some service process template which must be runned after process deployment into another environment. This process will change all parameters for all your processes so you will not need to place additional activities in each process. Don't forget that these additional activities can cause additional load on servers.

This is just an idea, I don't use it in my project and haven't tested enough.

~ Konstantin