I'm trying to figure out a way to use rest to retrieve a session ID created by a given analyst logging in with a browser.
I would like to be able to use a compound where clause something like:
(forgive the syntax i just copied it out of SOAP-UI)
In reading the documentation I don't see anything about compound where clauses or where clauses used simultaneously with the sort clause is either scenario possible?
Or is there another way to solve this problem?
session_type=1 is GUI based login.
Our sorting syntax is documented here: REST HTTP Methods - CA Service Management - 17.0 - CA Technologies Documentation
So a sample like this seems to be working fine for me, where I'm looking for the latest 50 GUI based logins records for a specific user. You can query / retrieve any objects on the session_log table below:
C:\>bop_sinfo -qd session_log
Factory session_log < session_log > Attributes: id INTEGER UNIQUE producer_id LOCAL STRING(20) persistent_id LOCAL STRING(60) login_time DATE REQUIRED logout_time DATE contact SREL -> cnt.id TENANCY_UNRESTRICTED session_id INTEGER session_type SREL -> session_type.id TENANCY_UNRESTRICTED policy SREL -> sapolicy.id TENANCY_UNRESTRICTED status INTEGER
Hope this helps
Thank you for your help!
I haven't been able to get any additional filters beyond sort to work before the WC.
For example below the sort and contact are working but session_type isn't, it doesn't make any difference where i put which attribute, only the sort plus 1 other will work.
I think I'm seeing the same too, could be a defect that we need to look into. Would you be able to raise a support case and hit me up with the #?
Sure, the case number is 00963268.
Sorry for the mislead. I do have your support case too, Looks like we did not know the correct syntax there.
We just needed %20AND%20 for the join, and it %3D instead of =.
So, a where clause like: contact='foo' and session_type=1 becomes contact%3DU'F4C2A60100EA154695D233F90ABFFD21'%20and%20session_type%3D1
See my working example below:
It was on the same docops page that I mentioned earlier but I totally missed it (REST HTTP Methods - CA Service Management - 17.0 - CA Technologies Documentation )
Hope that resolves yours too