Expected result: Complaint/case is successfully inserted and is displayed on top of fancy tree and is opened. Notification message is displayed: "Complaint/Case with ID {{id}} was created.", Actual result: Case/Complaint is not inserted. Fixed
2. Body panel in Reset Dialog need to have bigger height so that language selection can show all 11 languages, and check box should show at the bottom.
3. When click a drop down box in the Reset Dialog, then Ctrl-A, all options are selected as expected with Chrome; but not with IE. With IE, all fields including background fields outside dialog are selected. Fixed
Added organization is displayed in the table but error occur in the console and after refresh the added organization is not displayed in the table Fixed
"Hourly Summary" and "Cost Summary" text is overlapped with some arrow (UI) 1: Login as user that have permissions to time tracking module.
Actual result: "Hourly Summary text is overlapped with arrow icon. ("Cost Summary" text is overlapped with arrow icon."). Fixed
Links of referenced complaint/case/task/document redirect to dashboard 1: Login as user that have permissions to cases/complaints
Automated tasks should copy their attachments to the parent object when task is completed Ad-hoc tasks correctly copy their doc-tree to the parent object when the task is completed.
This does not happen for automated tasks (i.e. tasks generated by an Activiti business process). Instead an ActiveMQ exception is shown in the log. Fixed
Initiator of complaint can be deleted even though is mandatory 1: Login as user that have permissions to open Complaints
Expected result: Because Initiator is mandatory notification message is displayed that can't be deleted.
3 Scroll down to the Attachments section, right click on the desired folder, and select New Document, and then type of document.
"Action error" occurs when user cancels adding new, existing member, subgroup or delete group 1: Login as user that have permissions to admin module
Exception occurs when user try to add ldap subgroup in organizational hierarchy 1: Login with user that have permissions to Admin module
People Module - Complaint node - Link to the complaint is not OK In People module, Complaint node, hyperlink to the complaint is not working. It redirects to the Complaint module, but with error Fixed
People module - Cases node - Link to the case is not OK In People module, Cases node, hyperlink to the case is not working. It redirects to the People overview page.
Case/Complaint/Task can't be created if calendar configuration in admin is not enabled 1:Login with user that have permissions to Admin module
Time Tracking labels are not present Issue is present in Admin section, all labels for Time Tracking module are not loading. Fixed
People-Organization relation not presented in the table When adding person in organization module (or adding Organization in People module), relation (Association type) is not presented in the table automatically, but after "Refresh" button it is shown correctly. Fixed
Deleting member from LDAP group deletes that user on LDAP directory Admin panel, Security group, Organizational Hierarchy: need to remove group membership for a particular user from LDAP group, but when you select "Delete Member" (trashcan icon), it entirely removes the user from LDAP directory! Fixed
Adding same Organization", multiple times in the object When adding an Organization in some object (Case, Complaint, People), it is allowed for same organization to be added multiple times with different relations. But presentation in the table (People module, Organization node) is not working OK. Problem with Relation (Association type). Fixed
Adding same "Person", multiple times in the object When adding a person in some object (Case, Complaint, Organization), it should be restricted for same person to be added multiple times with different relations. Person object should be related only once with another object. Fixed
AFDP-3944 Save Configuration for System User Used for Folder Creation When an Outlook calendar folder is created, the data for the system user used for creating the folder should be recorded. Subsequently, when the object instance is accessed, the recorded data is used for retrieving the Outlook calendar folder. this will enable the system to change the system user without disrupting the access to the created calendar folders.
The recorded data for the system user should be encrypted, by using the encryption tools we have in the system. Further, the recorded data should not be stored in the object itself, but in a separate entity, to make it easier to update the password associated with the system user, if/when the password of that user is updated. Fixed
AFDP-3944 System User for Object Creation The system user configured for reading the Outlook calendar folder for given object type, should be used for folder creation as well. Also, calendar integration property should be taken into account as well. If calendar integration is not enabled for given object type, the calendar folder should not be created.
Since Outlook calendar folder creation is dependent on integration with outlook, the corresponding handlers should be moved in the `acm-service-calendar-integration-exchange` maven module. Fixed
Main User Menu options (left menu) are covered by "Powered by ArkCase" label *Description*: When an admin user is authenticated he has all app features and functionalities listed in the main user menu on the left nav bar, but not all of them are listed although the sidebar menu has scroll bar. Last option is not loaded at first and if you click the last option at that moment then other option will appear.
LDAP sync should determine membership through group "member" attribute instead of/ in addition to users and groups "memberOf" In order to detect user group membership changes during the partial sync, we should determine group membership through "member" attribute of the group, versus "memberOf" on the user. Since adding a user to a group doesn't change the user's "modifyTimestamp" only the group's "modifyTimestamp" and the current implementation won't catch any new members added to the changed group. LDAP users search should also make sure that all groups (top level and nested) in which an user is member are retrieved.
After search results are retrieved from the directory, result entries are updated or added in database. This implementation should be optimized to avoid unnecessary multiple "find" and "save" for the same entity to database which significantly slows down the synchronization completion.
After ldap sync is performed, these two fields are set to "null", thus the reset password link is no longer valid.
expected: The ldap sync shouldn't remove the generated token. The user should be able to reset the password until token validity expires. (according to cm_token_ex_date). Fixed
Problem adding existing user to the LDAP group There is a problem when you try to add user in "Organizational Hierarchy" on the "add existing member" button. (Admin/Security/Organizational History).
Please note that adding New Member is working fine, only adding existing member is trowing an error (400 Bad request). Fixed
Contacts Management – People - De-activate People The system shall allow the de-activation of any activated People(s) Fixed
Contacts Management – People - Activate People The system shall allow the activation of any de-activated People(s). Fixed
Once "Deactivate" is implemented, we can change the status to Inactive which is keep the Organization from displaying in the picker. Fixed
Organization > People > Add Person > Person Type. Change default label to Role Change the label to Role as it's the Person's Role within the Organization
People and Organization needs "Alt-text" and astericks "*" for mandatory fields for Section 508 - accessibility For New People and New Organization forms, mandatory field has to be marked ("alt-text", asterisks and red box around the field).
Organization module - People node functionality issues For the People node in Organization Module, there are few issues/defects that has to be fixed:
- form should be consolidated as other forms ("+" in the black header for adding new picture, "edit" and "Delete" buttons on the right of each line)
Complaints module - relation to People issues When adding new/existing person for the complaints module, there is a problem creating link to the people module. Can add a new person to the people table in the Complaint Module, but the complaint doesn’t show on the complaint table in the People module for that person.
Organization module - People node functionality issues For the People node in Organizations Module, there are few issues/defects that has to be fixed:
- Form should be consolidated as other forms ("+" in the black header for adding new people, “pen” (for edit), and “Garbage can” (for delete) ...buttons on the right of each line)
- There shouldn't be different buttons for adding new or existing people (on "+" a popup should open to choose "new" or "exsisting") Fixed
Organization module - DBA node functionality issues For the DBA node in Organizations Module, there are few issues/defects that has to be fixed:
- Form should be consolidated as other forms ("+" in the black header for adding new address, “pen” (for edit), and “Garbage can” (for delete) ...buttons on the right of each line)
(example: "Primary/not primary" column can be added with radio button for choosing the primary address) Fixed
Add Organization Node in "New People" Form Organizations node in New People form is not working Fixed
Subscription module Event column doesn't display event description I subscribed to case "New Case" as user "Sally Supervisor". I made two changes (changed the priority and due date) and then checked the Subscription module to see if these events show up.
Additionally, when I make a single change there are multiple results with the exact same timestamp. Since the Event description is the same I can't tell why there are so many. Fixed
AFDP-3202 Refine Label Configuration page in Admin Need to rework the language selection, locale selection, and reset buttons in Admin Label Configuration screen. UI may be confused to many users:
LDAP sync in Arkcase should use whenChanged field Using '*whenChanged*' field our sync process will only sync the changed user and groups after the last sync execution. For example in Alfresco we can set these properties:
Some of our cranks currently use a wave washer and spindle spacers to adjust the bearing pre-load and account for tolerance differences in individual frames. If too many spacers are used the bearings can be over pre-loaded resulting in excess drag Our newer cranks use our APS system for preload which functions a bit differently. Refer to the owners manual to ensure that your cranks are installed properly. If you think they are installed correctly and you still have questions, contact your local Hive dealer.
Hydro Protocol Token (HOT) will begin trading on Huobi HADAX (Huobi Autonomous Digital Asset Exchange) on May 7, 2018, at 2:00 PM (GMT+8), offered as BTC and ETH trading pairs.
“Huobi HADAX will take a snapshot of HT assets held in users’ accounts on May 7, 2018, at 2:00 pm (GMT+8), and perform an airdrop of 350,000 HOT to HT holders.
The above-mentioned airdrop of 350,000HOT will be divided across HT users proportionately according to their HT holdings. The airdrop will be deposited to the beneficiary HADAX trading account within 7 working days after the snapshot is completed.”
Please note: Hydro Protocol Token (HOT) shares the same token symbol with another token Holo (HOT). We would like to remind users that when depositing, trading or withdrawing HOT, please check the smart contract carefully to avoid any potential loss of your assets.
Documentation to understand the data model and data structures in the r8 Model Manager mart database for SQL querying
Title: we are looking for documentation that can help us understand the data model and data structures in the r8 Model Manager mart database for SQL querying.
How can we access the Model Manager database directly via SQL for a homegrown application? We would like to directly access the Model Manager database via a Java program. We are looking for documentation that can help us understand the data model and data structures in the Model Manager database. Are there any knowledgebase articles to help us?
Please see the attached spreadsheet (r8_MM_Sample_Queries.xlsx) listing some SQL queries that you can use to help figure out how to construct your Model Manager queries.
Now you can view and access the SQL that is behind the report. You can even modify the SQL and save that as a new report, if you like.
Try Reverse Engineering the mart db using erwin to form a model for your Team to view to help understand your joins.
Another idea is to create a new mart on a second db (no additional mart license is necessary so long as the same users access the second mart) and populate it with a very simple one entity model. Then add a new object / property to that model, save changes to the mart, and query that database.
Please note that erwin builds many inherited values in a model using memory. Inherited values that flow down relationship chains or from domains or from logical to physical are most likely not stored in a mart. Model Manager will not store a physical name or object unless the inheritance has been manually broken by a modeler, and a unique value typed in by hand. The reason for that is the Model Manager does not store the complete model diagram as it is presented in erwin. It stores only the information required to construct the complete model diagram. Therefore it is not possible to query the Model Manager on most physical or other inherited data unless the inherited data is manually changed or the modeler hardens the physical data beforehand.
Article ID: 3410 Security Report query for r8 and r7 marts. Produces a report of all the mart users and what levels of security they have been granted in a mart. That Security Report query may also be used to help compare an r8 / r7 mart set up with the upgraded users and profiles in your new r9 mart.
Article ID: 3893 We are looking for documentation that can help us understand the data model and data structures in the r9.x mart database for SQL querying.