Testing of HPE RM8.3.0.9000 - Few issues so far in mixed environment

Hi, 

HPE RM8.3.0.9000 manually installed, Development server 8.2.0.7591 built, MS Office 2010, Win 7, SQL 2012-R2

Ok, so far, all looks OK in my 150 test plan scenario .... 

Old issue from HP RM8.1.7760 are fixed (except Requests not being deleted once the file is assigned)

New, very handy features are also tested (not all, but the ones we are interested in) and it looks very good. 

Ok, in this mixed environment my tests revealed these issues: 

Recent documents - not showing up, not sure where to check this(if there is an option to tick) 

New spell check will fix always the first word (e.g. if we have word "client" twice misspelled, it will always try to fix the first one even if is already fixed, even when we click to select the second "client" word in the title... minor, but.. 

Ok, bit more serious one: We have a Picture Set record type level 3 ... cannot be created / placed within the Corporate File level 4 container.... Big issue... In 8.1 and 8.2 this issue does not exist. 

the last one:    some lookup items for additional field - from the lookup set cannot be selected, some error "Filed "issue" ): must match one of the predifined lookup set values...

That is all for now...

Anyone had similar issues or know how to fix these.. We are about to make decision to go for 8.2 or 8.3 

Regards

 

 

 

Parents
  • Try in a full 8.30 environment and see how you go.

    Mixed environments might see issues and are never supported.

  • Thanks, 

    8.3 environment not built yet, maube in a week or so... 

    So far these3 issues are the only one 

    Cheers

     

  • Dang, this is a deal breaker for us. Due to upgrade in 4 weeks, now need to make a call on upgrading to 8.2 (which has other crappy limitations) or waiting until a new build of 8.3 is out ... more planning out the window...  :(

     

  • Well, there is a hope since other users do not have these sort of issues, e.g. HP Support cannot replicate the error, so it must be some small thing/settings that was changed when database/dataset were coppied or ..some setting that is on the client side...

    We are in the similar situation regrading which client we are going to roll out...

    8.3 supports Win 10 and MS Office 2016 and SharePoint edit integrations

     

  • Think that I have discussed this before with someone on the forums, can't remember if it was yourself but the "picture set" record type seems familiar.

    In any case the problem lies in the system settings.

    Administration > system > miscellaneous > "when placing a record within a container"

    "records that behave as a document can only be contained within records that behave as a folder" might be checked.

    You will need to uncheck that option, close records manager and test again.

  • Waoh, that did the trick...

    Any side effects?

    Because, this is checked in production and i do not have any problems in HP RM8.1 production

    Thanks

     

  • Helpful tip, when you are in the system options and you hit the 'Help' button it will take you to the relevant chapter in the helpfile. eg this is what came up when I hit help:

    When placing a Record within a Container (or allocating to a Category):
    Records that behave as documents can only be contained within Records that behave as folders - not selected by default.
    When this option is selected:

    When user are selecting a container for a record that behaves like a document, they will only be allowed to select a record that behaves like a folder;
    -- and --

    Document Record Types will not be available when users are creating a new record within a Category browser;
    -- and --

    The Record Types available to users for this method of creating new records are restricted to those that:
    number by container
    -- or --

    have the command Category selected.
    Note: This means that you can hide Record Types from this list by making the command Category unavailable for the selected Record Type.

    When a user creates a record that has a preset Category or container, they will not be able to change the selected Category or container.

    "Give a man a fish and you feed him for a day; teach a man to fish and you feed him for a lifetime."

  • Excellent! Thanks Greg

    Any chance you know of a similar system option stopping things going into the 'recent docs' also :)

  • In HPE RM8.3.9000  

    There is an error "This location can not be used for assignee" when trying to assign the Corporate File to an Average user location type, not expired, full employee, 

    The File access is set to "Everyone" 

    What could be the issue here?  Hope this is not a show stopage .... The file can be assigned to An Administrator user type... or to a user that belongs to a Records 

    Record type properties : Update records metadata People in File Creator or Records

    Thanks

     

     

     

  • Once I checked the option on that particular Corporate file "Bypass Record type access control refferences" I could assign it to everyone/any location but that is not tha answer

     

  • This is an issue with what is being referenced on the Record Type or Classification default access settings.

    You'll need to change the record type or classification to possibly resolve this long term.

    Otherwise, bypassing the record type references IS the correct solution.

  • Thanks, we cannot do bypassing the record type references. I will explore the settings in the Classifications and Record type

Reply Children