search

jlabbe-processia / mxupdate

Automatically exported from code.google.com/p/mxupdate
1 stars 1 forks source link

Performance enhancement for policy configurations ( export functionality ) #171

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. export policy CI
   from CI file you can see that user accesses are sorted alphabetically
2. import CI back to schema
   from policy settings you can see that user accesses are in reverse order
3. modify user accesses to provide better performance by using known core 
feature
   - specifying the mostly used 'user access' as last one and 'user access' with "TrickyFilter" to first
     e.g.
      mql add policy "TEST" \
      state "Created" \
        Owner Read, Show \
        Public Show \
        add user "Employee" Read, Show \
        filter "TrickyFilter" \
        add user "Designer" Read, Show, Modify \
        filter "SimpleFilter" \
        add user "SuperUser" All
   - create multiple business objects using this kind of policy CI
   - verify performance by searching objects
4. export policy CI by using MxUpdate tool export functionality (already now 
you can see that user accesses are sorted alphabetically)
5. import policy CI back to schema using MxUpdate
6. verify definitions from schema (you can find that user access 'Employee' 
using "TrickyFilter" is the first one)

What is the expected output? What do you see instead?
   - when exporting policy configurations to CI file order from schema should be taken in count by understanding the core feature
   - this means that if user access is shown as first one there in schema, it needs to be shown as last one there in CI file

What version of the product are you using? On what operating system?
   Enovia V6R2012x.HF11
   MxUpdate Update Deployment Tool V0.10.0 (with latest revision 854 and unOfficial fix)

Please provide any additional information below.
   - import functionality works as needed, but there are needs to enhance export functionality
   - when using this kind of way of ordering you may get huge performance benefits, e.g. query taking originally 10 mins takes later less than 2 mins

Original issue reported on code.google.com by yrtti...@gmail.com on 10 Jul 2012 at 7:00

GoogleCodeExporter commented 8 years ago 
As DS is not supporting this officially with newer versions, this ticket can be 
closed.
...to be opened again in case of need.

Original comment by yrtti...@gmail.com on 30 Sep 2013 at 5:23

GoogleCodeExporter commented 8 years ago 
The order defined from MX is now used. No automatically sorting is done (but 
can be defined manually from the user).

Original comment by tim.mox...@innobix.com on 7 Oct 2013 at 12:29

GoogleCodeExporter commented 8 years ago 
New MxUpdate version is available.

Update of the Documentation is needed.

Original comment by tim.mox...@innobix.com on 8 Nov 2013 at 10:31

GoogleCodeExporter commented 8 years ago

Original comment by tim.mox...@innobix.com on 8 Nov 2013 at 10:32

GoogleCodeExporter commented 8 years ago

Original comment by tim.mox...@innobix.com on 7 Feb 2014 at 8:30