Submitted two database-related enhancement requests

[Peter Heggie]

I’m wondering if anyone else thinks these are useful enhancement requests, related to DB protocol.

1) Configuration variable lookup table:

Establish a lookup table (ex: hci_admin_configuration.tbl) that is used to store variables that are resolved at key times like process startup time or Box migration. First use – Translator Configuration that references a Database schema for the inbound or outbound side. Allow the DB Connection name value to be represented by a variable (ex: @hci_db_connection) whose value is stored in the new table. When a Translate is copied from one site to another, you will no longer get errors when the related DB VRL cannot be found because the DB Connection is different (for example between a test SQL Server and a prod SQL Server). This kind of functionality is required for the Box function to be automated. Otherwise you will always have manual intervention required. This new dynamic resolution capability can be rolled out to other functions in a priority order tied to automating Box functionality/object types.

2) DB Protocol Configuration GUI to include stored procedure discovery & mapping

Update the GUI that formats thread DB protocol configuration, to include mapping schema elements (i.e. elements in a DB VRL) to elements in a SQL statement, whether that statement is raw SQL or arguments in a stored procedure. So there are two new things here – a mechanism that discovers table columns or discovers stored procedure arguments, and a mapping GUI that allows an administrator to map the these columns or arguments to VRL elements. The mapping should allow for literals to be used in place of variables. This makes it easier to configure stored procedure invocation, and it may also be easier for some people to understand how to connect the VRL to the database elements.

Also, optionally, as referenced in Enhancement Request 7000671, system variables could be used in place of these variables, or to identify the schema, to allow for resolution at process startup time.

For the first one – every time I copy a translate, using a DB VRL, from Test to Live, I get hit with the error message where the configuration is in error due to a missing schema / vrl, and I have to reconfigure it. It is not a big deal but it means it is not portable, and Box migration cannot be automated.

For the second one – when configuring the DB protocol, you have to know the order of arguments between the vrl/schema, and the database stored procedure. The enhancement would make it easier to setup.

Peter

Peter Heggie

Topic

[Max Drown (Infor)]

Sounds useful to me!

-- Max Drown (Infor)

[Ga]

Hi Peter,

Take a look on my reqest ‘DB Outbound Protocol : Need help to format my Sql Insert req Posted: Fri Mar 28, 2014 12:36 pm ‘.

Thanks

[Author]

Replies