Announcement

Collapse
No announcement yet.

Removing Saved Queries from Finder List

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Removing Saved Queries from Finder List

    We have been using OTM for a few years and over time we have accumulated quite a long list of saved queries for various different uses (for specific Order Release searches). We recently started cleaning up many of the unused saved queries and put a list together of the ones we still use and the ones we no longer need (at least for now).

    We are trying to reduce the number of saved queries each user sees when they expand the saved query search list at the bottom of the OTM window. We do not want to delete the saved queries yet until we determine if they can still be used or if they should be deleted. But in the meantime, we would like to reduce the size of this list because it causes users to have to search through many queries and could sometimes result in the user selecting the incorrect query.

    We have gone into multiple saved queries and removed the "Use in Finder" check from the box but this does not remove the query from the list and the query actually remains active if selected from the list. We also changed the glog.properties setting from TRUE to:

    glog.savedquery.show_all_savedqueries=false

    However, this still did not work (even after bouncing the App server) and we still see the saved queries in the list.

    Can somebody tell me if it is possible to remove these saved queries from the Finder list without actually deleting the saved queries from OTM?

    Thanks.

  • #2
    Re: Removing Saved Queries from Finder List

    Hi ,

    This can be done by restricting the saved queries for a particular user,level or role using the 'manage user access' functionality.
    Warm Regards,
    Srivathsana

    Comment


    • #3
      Re: Removing Saved Queries from Finder List

      Hi cspadola

      Is the solution given by Srivathsana working fine??

      Rgds
      Sophia

      Comment


      • #4
        Re: Removing Saved Queries from Finder List

        We found out that these saved queries cannot be removed from the list. By using or not using Show in Finder, all that is happening is manipulating how the sql in the Check One SQL and Find All SQL is working.

        In the end, our solution to this was to create different groups of users that could access specific groups of screens. In each screen, we added the different saved queries the group will use and when each user logs in to OTM, they will be automatically set to that group. This seems to work fine for us because our planning team is divided into different geographical regions and the saved queries each region uses is specific for their group.

        Comment


        • #5
          Re: Removing Saved Queries from Finder List

          Firstly, glog.savedquery.show_all_savedqueries should work if it is set to FALSE on App server.
          Try to remove the property from glog.properties, since FALSE is default value.

          Secondly, Saved Query Access is a good approach if users do not need to define their saved queries.

          If you need to define some saved queries via SQL for users, also allow them to create their own saved queries via Finder, you may consider the way I am using.

          The approach is based on VPD, with glog.savedquery.show_all_savedqueries=TRUE
          I create two EXPERNAL PREDICATE for SAVED_QUERY table.
          1) READ:
          User can only see Saved Queries start with "0_" or created by himself or are in Public domain.
          Code:
          (  SAVED_QUERY.saved_query_xid like '0/_%' escape '/'
          or SAVED_QUERY.insert_user=sys_context('gl_user_ctx','gl_user_gid') 
          or SAVED_QUERY.domain_name='PUBLIC')
          2) UPDATE:
          User can only modify Saved Queries created by himself.
          Code:
          (SAVED_QUERY.insert_user=sys_context('gl_user_ctx','gl_user_gid'))
          Set the following property on OTM Web to avoid Saved Queries being cached.
          glog.properties
          Code:
          glog.webserver.savedquerynamecache=false
          Please note that with this approach, all Allowed Conditions used by Action Checks must be visible to the users.
          Last edited by josephliang; October 13, 2009, 03:55. Reason: added glog.webserver.savedquerynamecache=false
          --
          Joseph Liang
          MavenWire APAC
          http://www.mavenwire.com/

          Comment


          • #6
            Re: Removing Saved Queries from Finder List

            Originally posted by josephliang View Post
            Firstly, glog.savedquery.show_all_savedqueries should work if it is set to FALSE on App server.
            Try to remove the property from glog.properties, since FALSE is default value.

            Secondly, Saved Query Access is a good approach if users do not need to define their saved queries.

            If you need to define some saved queries via SQL for users, also allow them to create their own saved queries via Finder, you may consider the way I am using.

            The approach is based on VPD, with glog.savedquery.show_all_savedqueries=TRUE
            I create two EXPERNAL PREDICATE for SAVED_QUERY table.
            1) READ:
            User can only see Saved Queries start with "0_" or created by himself or are in Public domain.
            Code:
            (  SAVED_QUERY.saved_query_xid like '0/_%' escape '/'
            or SAVED_QUERY.insert_user=sys_context('gl_user_ctx','gl_user_gid') 
            or SAVED_QUERY.domain_name='PUBLIC')
            2) UPDATE:
            User can only modify Saved Queries created by himself.
            Code:
            (SAVED_QUERY.insert_user=sys_context('gl_user_ctx','gl_user_gid'))
            Set the following property on OTM Web to avoid Saved Queries being cached.
            glog.properties
            Code:
            glog.webserver.savedquerynamecache=false
            Please note that with this approach, all Allowed Conditions used by Action Checks must be visible to the users.
            Joseph,

            One question to the approach you have suggested here. Does putting the predicates on the saved_query table affects the saved query's created by one user that is been used in agents which is common to the domain.
            Regard's
            Arun

            Comment


            • #7
              Re: Removing Saved Queries from Finder List

              VPD affects EVERYTHING, including Saved Queries in Agents, Allow Conditions in Action Checks,...
              --
              Joseph Liang
              MavenWire APAC
              http://www.mavenwire.com/

              Comment


              • #8
                Re: Removing Saved Queries from Finder List

                Yes - Joseph is completely right. It affects every query in OTM.

                --Chris

                Comment


                • #9
                  Re: Removing Saved Queries from Finder List

                  Originally posted by josephliang View Post
                  VPD affects EVERYTHING, including Saved Queries in Agents, Allow Conditions in Action Checks,...
                  Thanks for reply Joseph. Any alternatives for that so that it wont affect the saved queries on the agents.

                  My requirement is this, Users whoever logged into OTM should be able to create/edit saved queries that is visible to them alone. Also Superusers who create saved queries should be visible to all users but only the superusers can create/edit/delete those.
                  Regard's
                  Arun

                  Comment


                  • #10
                    Re: Removing Saved Queries from Finder List

                    By default, Agents are executed by ADMIN user of the domain of the object. For example, Order AAA.ORDER1 will be executed by AAA.ADMIN
                    Thus, for READ predicate you can try
                    Code:
                    ((sys_context('gl_user_ctx','gl_user_gid')='AAA.ADMIN') or (sys_context('gl_user_ctx','gl_user_gid')<>'AAA.ADMIN' and ...))
                    But please keep in mind that VPD affects everything in OTM. Above only handles Saved Queries in Agents.
                    --
                    Joseph Liang
                    MavenWire APAC
                    http://www.mavenwire.com/

                    Comment


                    • #11
                      Re: Removing Saved Queries from Finder List

                      Hi Happy New Year,
                      Hope everyone is doing good...!
                      I have a small Issue which is bit wired.
                      I have created some Saved Queries, but the problem is like I can't able to see in the Order Release Finder(they are checked with "Use in Finder" in the Query).
                      Actually we have a Bounce twice a day.
                      I can see few old once that too they are not fixed.Queries are differing for every Bounce.
                      I'm using 6.2.4 version.
                      Can anyone HELP me in this case.

                      Thanks in Advance..

                      Comment


                      • #12
                        Re: Removing Saved Queries from Finder List

                        Hi Nikhillyen,

                        Not sure if you resolved this issue or not: you may leverage use of following property per your need:

                        glog.savedquery.show_all_savedqueries

                        Determines if queries marked with the Use in Finder check box not selected show up on the finder screen in the saved query drop-down list. When this property is set to FALSE, any queries with that check box not selected will NOT be shown on the associated finder. In order to get queries that do not have their Use in Finder check box selected to show up on a finder, set this property to TRUE.
                        Thank You,
                        cshah8

                        Oracle Certified OTM 6 Implementation Specialist
                        ------------------------------------------------------------------
                        If my post was useful please click Thanks!

                        Comment

                        Working...
                        X