nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

xCP 2.0 and registered tables

artika4biz

I would like to specify a DQL statement when I create a new a real-time query: it seems that the xCP developer can "just" compose the real-time query visually; is there a way to use explicitly a DQL statement? Is there a way to query a registered table?

Thanks for sharing!

Yuri

Find more posts tagged with

Comments

pettitk

You use a stateless process. W a dql read activity.

Kyle Pettit

Sent from my iPhone-please excuse any typos.

artika4biz

Thanks Kyle.

Actually I would avoid stateless processes because sometime they are not enough fast to be used in a dynamic gui. I hope that a future xCP release will implement DQL real-time query.

prabhu

Real Time Queries are meant only for the application objects. So why not use Business Object model instead of Registered Tables ?

artika4biz

Sometime it is useful to query external table from a different database, instance

pettitk

I still don't fully understand your requirements, but assuming your want to use this in GUI, like to populate a picklist or something, Stateless Processes are your answer for hooking into registered tables.

Actually, stateless processes run rather quick in everything I have seen so far. Sure we are not in production yet, but the testing we have done so far, we are running at an acceptable speed. We render a form with about 50 fields on it. About 7-8 of them are stateless process queries and 1-2 them over 100 entries in the resulting list. The notion of Stateless Process is new to 7.0/XCP2 with some very impressive performance gains. It actually has very little hit to the CS or JMS and is negligible (so far). I had the same doubts too at first.. .What, build my picklist from a workflow process? Sounded absurd at first, but it actually works fine for us.

If your results are rather large (greater then 100 or 200), you may have to get creative with sub-selects or something to keep the query time down, etc.

If your registered tables, however, are NOT in the same database, I would not recommend hitting them directly. Rather, best practice would say to copy those tables to Documentum on a frequency that is acceptable. I have done that for many clients. The lowest interval we did was 1 hr, but IMO, 1 day is often good enough to refresh the registered table. If its local to the database, you will find the performance alot better, especially on a larger table. A good dba can do that in a matter of minutes, and set it up so that it runs as a batch on your desired interval.

Best of luck

dnvhariprasad

Sure we are not in production yet, but the testing we have done so far, we are running at an acceptable speed. We render a form with about 50 fields on it. About 7-8 of them are stateless process queries and 1-2 them over 100 entries in the resulting list.

Hi Kyle,

I dont mean to hijack this thread but I would like to know how did you do the testing in your xcp2.0 application? would you mind to share your thoughts?

pettitk

There wasn’t any formal testing of this fact… just how long does it take the page to render for a user… which was less the a few seconds, thus acceptable. No formal timing. This xcp2 project is actually on hold for us right now so I can’t get into it to actually run a test right now or I would.

pettitk

Yes very useful, and we use it all the time. We just do it by batch copying the table to the local DB for performance reasons. I have had an Oracle Documentum DB linked too other Oralce, Sybase, and SQL Server sources at the same time. For that situation, it was for a large state government client, and like many customer, they had an array of DB’s in their environment. In all cases, we copied the tables to local Documentum DB, to insure better performance. Using linked DBs was unreliable for us.

I am sure its possible that sometimes it may not be allowed, or just not feasible for whatever reason to copy the table. In such case, I guess you have to grin and bare the performance hit.

Best of luck with your project,

Regards

Kyle