Page Comparison

API Changes:

• AN-2220: All the filters in the asta requisition should be same.
  

  Code Block

  1. Previous Endpoint: `/api/workflow?organizationId=1` - Current Endpoint: `/api/workflow?organizationIds=1,2` - Explanation: In the previous version, this endpoint retrieves workflow data for an organization with ID 1. In the current version, it's updated to retrieve workflow data for organizations with IDs 1 and 2, allowing data retrieval for multiple organizations simultaneously. 2. Previous Endpoint: `/api/customer?organizationId=1` - Current Endpoint: `/api/customer?organizationIds=1,2,3` - Explanation: Similar to the workflow endpoint, the previous version retrieves customer data for an organization with ID 1. In the current version, it's modified to fetch customer data for organizations with IDs 1, 2, and 3, accommodating multiple organizations. 3. Previous Endpoint: `/api/requisition/getAllRequisition?location=RA&stateId=1&firstItemStateId=1&typeId=1` - Current Endpoint: `/api/requisition/getAllRequisition?locations=RA&stateIds=1&firstItemStateIds=1&typeIds=1,2` - Explanation: This endpoint retrieves all requisitions with specific location, state, first item state, and type IDs. In the current version, the parameters are pluralized (`location` to `locations`, `stateId` to `stateIds`, `firstItemStateId` to `firstItemStateIds`, `typeId` to `typeIds`), allowing for multiple values for each parameter. 4. Previous Endpoint: `/api/requisition/requisitionItems/{requisition_id}?location=RA&stateId=1` - Current Endpoint: `/api/requisition/requisitionItems/{requisition_id}?locations=RA,RH&stateIds=1` - Explanation: This endpoint retrieves requisition items for a specific requisition ID, with specific locations and state IDs. In the current version, the parameters are pluralized (`location` to `locations`, `stateId` to `stateIds`), allowing for multiple values for each parameter. 5. Previous Endpoint: `/api/export/requisitions/print-items?location=RA&stateId=1&firstItemStateId=1&typeId=1` - Current Endpoint: `/api/export/requisitions/print-items?locations=RA&stateIds=1&firstItemStateIds=1&typeIds=1,2` - Explanation: Similar to the `getAllRequisition` endpoint, this endpoint exports requisition items with specific location, state, first item state, and type IDs. In the current version, the parameters are pluralized (`location` to `locations`, `stateId` to `stateIds`, `firstItemStateId` to `firstItemStateIds`, `typeId` to `typeIds`), allowing for multiple values for each parameter.

...

• AN-2229: Optionally make it possible keep all requests to Asta 7 in a log on disk
  

  For adding custom nginx log in data disk, we need to follow below steps

  • First create folder in /data with name asta7_nginx_log

  • Initially the ownership of the folder will be root, we must change the ownership to user otherwise gui-pt will not work

  Code Block
  language bash
  sudo chown -R $(whoami):$(whoami) /data/asta7_nginx_log

  • in the docker-compose we already have volume mount in gui-client which will mount this folder to container and we will have log in data disk

    Code Block
    volumes: - ~/.asta7-ssl:/etc/nginx/ssl - /data/asta7_nginx_log:/var/log/nginx

  • for rotating log of nginx in data disk we will use logrotate in linux, to setup this follow below command

  Code Block

  sudo apt install logrotate sudo nano /etc/logrotate.d/asta7 /data/asta7_nginx_log/*.log { weekly compress create 0640 ubuntu ubuntu copytruncate dateext su root adm missingok notifempty } # to spot our logrotate configuration sudo logrotate /etc/logrotate.conf --debug # to Test without waiting sudo logrotate -f /etc/logrotate.d/asta7 # in the "/data/asta7_nginx_log/" we will find backup file of the log and original file become empty

• AN-2220: All the filters in the asta requisition should be same.
  

  Code Block

  1. Previous Endpoint: `/api/workflow?organizationId=1` - Current Endpoint: `/api/workflow?organizationIds=1,2` - Explanation: In the previous version, this endpoint retrieves workflow data for an organization with ID 1. In the current version, it's updated to retrieve workflow data for organizations with IDs 1 and 2, allowing data retrieval for multiple organizations simultaneously. 2. Previous Endpoint: `/api/customer?organizationId=1` - Current Endpoint: `/api/customer?organizationIds=1,2,3` - Explanation: Similar to the workflow endpoint, the previous version retrieves customer data for an organization with ID 1. In the current version, it's modified to fetch customer data for organizations with IDs 1, 2, and 3, accommodating multiple organizations. 3. Previous Endpoint: `/api/requisition/getAllRequisition?location=RA&stateId=1&firstItemStateId=1&typeId=1` - Current Endpoint: `/api/requisition/getAllRequisition?locations=RA&stateIds=1&firstItemStateIds=1&typeIds=1,2` - Explanation: This endpoint retrieves all requisitions with specific location, state, first item state, and type IDs. In the current version, the parameters are pluralized (`location` to `locations`, `stateId` to `stateIds`, `firstItemStateId` to `firstItemStateIds`, `typeId` to `typeIds`), allowing for multiple values for each parameter. 4. Previous Endpoint: `/api/requisition/requisitionItems/{requisition_id}?location=RA&stateId=1` - Current Endpoint: `/api/requisition/requisitionItems/{requisition_id}?locations=RA,RH&stateIds=1` - Explanation: This endpoint retrieves requisition items for a specific requisition ID, with specific locations and state IDs. In the current version, the parameters are pluralized (`location` to `locations`, `stateId` to `stateIds`), allowing for multiple values for each parameter. 5. Previous Endpoint: `/api/export/requisitions/print-items?location=RA&stateId=1&firstItemStateId=1&typeId=1` - Current Endpoint: `/api/export/requisitions/print-items?locations=RA&stateIds=1&firstItemStateIds=1&typeIds=1,2` - Explanation: Similar to the `getAllRequisition` endpoint, this endpoint exports requisition items with specific location, state, first item state, and type IDs. In the current version, the parameters are pluralized (`location` to `locations`, `stateId` to `stateIds`, `firstItemStateId` to `firstItemStateIds`, `typeId` to `typeIds`), allowing for multiple values for each parameter.

• AN-2138: Include created field when migrating content from Asta 5 to Asta 7
  
  1. Use below query to export archive units created field value and save it to a file such as archive-unit.csv

  Code Block
  select ARKIVENHET.ENHETSTYPEENHETSTYPEID, ARKIVENHETURN.URN, ARKIVENHET.OPPRETTETDATO, ARKIVENHET.OPPRETTETAV from ARKIVENHET inner join ARKIVENHETURN on ARKIVENHET.ARKIVENHETID = ARKIVENHETURN.ARKIVENHET_ARKIVENHETID;

  
  2. Use below query to export archive units created field value and save it to a file such as

  aktor.csv

  Code Block
  select AKTORURN.URN, AKTOR.OPPRETTETDATO, AKTOR.OPPRETTETAV from AKTOR inner join AKTORURN on AKTOR.AKTORID = AKTORURN.AKTOR_AKTORID;

  
  3. Run the following script after replacing

  ARCHIVE_UNIT_FILE, AKTOR_FILE and PROJECT_ID variable value.
  
  

  View file
  name isadg_created_field_fix.sh

• AN-1943: Improve search to include member and system entities 2197: Save Object Information For Portal Requisition In Asta Requisition and Support Sync Issue as well

  Code Block

  NeedThe touser re-indexmust allLOAD theportal initializedrequisition projectsto (basedadd onthe settingsobject_info itand mightrestriction take some time to finish). Changes made in the Participant Module settings Only the Aktor entity is searchable. The rest of the entities are part of the Aktor entity. Changes made in the ISAD(G) entity settings Only the main entities (Arkiv, Arkivdel, Serie, Stykke, Mappe, Aksesjon, Tilvekst) are searchable. The rest of the entities are part of the main entities. Possible consequences on the saved searches due to the changes made As the basic search filter now supports a single project only, any saved search having multiple projects will no longer work. Any saved search made using the entities that are no longer searchable will not work.

  AN-2197: Save Object Information For Portal Requisition In Asta Requisition and Support Sync Issue as well

  Code Block
  The user must LOAD portal requisition to add the object_info and restriction data data in the table. It will insert data in the background so that portal requisition will not call asta7 for shelf-marker data every time. The user can sync from the sync button in the requisition from the requisition portal if any data gets updated.

...

1. Stop the previously running Asta7

   Code Block
   cd previous_asta7_directory docker compose down

2. Download and extract Asta7 1.63.0

3. Adjust the .env file according to the previous one

4. Run Asta7 1.63.0

5. After running need to do sync in the asta-requisition.
   

   Image Added

   Code Block
   cd asta7-1.63.0 docker compose up -d

...