Hi @InfFilipV Not in the workspace though, but you will be able to find the third party JAR files in Build home in following locations: Build\Home\source\fndbas\server\libBuild\Home\source\fndbas\framework\thirdparty /Harshini
Hi @EntMethAb Hope you performed the steps carefully and performed “Synchronize Libraries” step as well and all the jar files got synced into your local workspace without any issue. Hope you selected the “Docker” option from technologies but nor Kubernetes. https://docs.ifs.com/techdocs/22r2/060_development/050_development_tools/002_developer_studio/030_reference/600_java_debugger/https://docs.ifs.com/techdocs/22r2/060_development/050_development_tools/002_developer_studio/020_project_setup/080_technologies/ /Harshini
Hi @EntMethAb It’s not nice to get those errors, but you can ignore the errors it seems, the functionality works works fine even with these errors.May be OData team can give us the reason for these errors thrown by OData and FSS. tagging @chanaka-shanil and @kosaladesilva /Harshini
Hi @Tracy Norwillo Hope following information in techdoc will help you to handle your requirementRemove Obsolete Objects Section¶This section should be placed at the end of the UPG file. Here obsolete views, packages, report tables, temporary tables, indexes, constraints and sequences can be dropped. Developers should never 'drop' any columns or tables that could cause data loss for the customer. Instead, there are methods in Database_SYS for obsoleting these two objects, Obsolete_Column and Obsolete_Table. These methods drop constaints etc. and renames them with a certain pattern. Columns are prefixed with OBSOLETE_COLUMN and tables with OBSLETE, but also suffixed with the component name. The removal of the renamed objects should be handled in the <Component-short-name>cl.sql file (clear-script). https://docs.ifs.com/techdocs/22r2/060_development/027_base_server_dev/007_concepts/200_upgrade_scripts/020_cdb_files/#remove_obsolete_objects https://docs.ifs.com/techdocs/22r2/060_de
Hi @Tracy Norwillo “404 Not Found” errors are there for non working links which need to be fixed. tagging @ChanakaAmarasekara , any comments on following? Is there any advice on removing the report model related files like the .rdf, xsd, and report projection?\/Harshini
@ChanakaAmarasekara , if you want to remove .report model file you can always obsolete the model file using the Navigator RMB option “Obsolete File” in Developer studio tool
Hi @stedile.jefferson Yes, we have done windows 11 21H2 certification testing for Developer studio. You can install the tool in Windows 11 21H2. it works fine. /Harshini
Hi @anushakh You may provide the IFS Dev credentials, from Build place, as you can see in the screenshot attched by the reporter of this post. @HDZANUSHAKH you have not given the service.
Hi @corie can understand your concern, When you click RMB on core files, there is this option called “Find File”, at least if we can make that option enabled, you will be able to locate the required core file. Also will check the possibility of making “Select in Projects”. enabled as well. Will keep you updated. I will create an internal task for this and check the possibility of implementing this back for core-cust separated environments/. ThanksHarshini
internal request created for this to check the feasibility : https://ifsdev.atlassian.net/browse/DXDEV-2925
Hi @InfFilipV This is not an error, this is a new functionality we have introduced in the tool to notify developers if there is a mismatch between the target version set in the project and the target version of the file in the checkout. In this case your project target version is set to 22R2-GA, but the target version files in the workspace is 22R2-EA. That is the reason for getting this message in the tool. If you are fine to go ahead just click YES. Please refer the section “Multiple Track support in DevStudio (Target version and DB change notification)” in https://docs.ifs.com/techdocs/22r1/060_development/050_development_tools/002_developer_studio/030_reference/920_new_tool_features/ Best RegardsHarshini
@InfFilipV make sure you are pointing to the correct core code files folder in the project properties first check the version of the CORE source code given in above folder path “Core files” found in fndbas/build/build.properties. If it is GA then, the tool should not popped up this message. If it’s something else then you need to check the downloaded zip file. if the zip file is incorrect need to contact the release management team.
@Daham , can you take a look on this issue please/Harshini
@Chamilka @Naleen Can you please take a look on this?
hi @Kenneth Pettersson CGI Unfortunately Developer Studio tool still do NOT support unit testing capability for customizations. Therefore you cannot include .pltst files in to your CUST model files. That is the reason of getting “PLTST does not contain any unit tests!” when try to run. We will do the necessary changes in the tool inform developers when they try to add a unit test to cust layer. Thanks for informing. RegardsHarshini
Hi @LevFredrB Also you can regulate this capability from Tools> Options menu/Harshini
Hi @InfFilipV This is now addressed in the latest tool version available in Developer portalVersion: 22.2.9262 or above.Better check for tool updates and update the tool thanksHarshini
Hi @HasithM When overtaking and overriding , you can't change the method signature. Signature should be as it is. That is the reason of getting the error “Method signature not found”. If you want to change the method body completely you can overtake the method and change the content of the body but should not change the method signature. If you need to add new parameters, implement a new method. /Harshini
@NxYavuzA , disconnect from the Global protect when you are trying to get connected for the first time. Then it should work. pls follows the steps given in the answer and give it a try.IF not working just test the DB and see whether you can login to it using SQL Developer. /Harshini
Hi @aNm ,In IFS Cloud we have all components installed, but that does not mean all components are ACTIVE for you. Activation and deactivation of components depends on the content of solution set file. You can work with in the components which are in ACTIVE state in solution set and disabled component are not available to use. Also make sure dynamic component dependency is properly set in deploy.ini file, and the correct set of components are enabled in solution set file. Refer to following techdoc pages for more details.https://docs.ifs.com/techdocs/22r2/060_development/050_development_tools/002_developer_studio/030_reference/900_solution_set/#code_generation1.https://docs.ifs.com/techdocs/22r2/020_lifecycle/070_self_service_options/020_updating_sol/2.https://docs.ifs.com/techdocs/22r2/070_remote_deploy/030_patching_system/100_solution_set/#installer_handling_of_solutionsetyaml_for_middle_tier And the community post: Hope above information will be useful to resolve the issue. ThanksHa
What do you mean ALL components in ACTIVE state? where? In Module_Tab?Now in Cloud we install all components irrespective of the content of solution set. /Harshini
In my solutionset.yaml file, 159 components are set to False.I checked Module_tab in DB and I have all modules ACTIVE=trueIs it normal?This is NOT NORMAL.Usually in Module_tab it lists down both ACTIVE and Deactivated components, All components do not set to ACTIVE state. Seems like there is an issue in the build and deployment. Pls refer to attached screenshot. this is how it should be and the content of the solution set file has to be taken into consideration. You will be able to get more information about solution set and deployment from this link.https://docs.ifs.com/techdocs/22r2/070_remote_deploy/030_patching_system/100_solution_set/#installer_handling_of_solutionsetyaml_for_middle_tier Hope this information will be useful. /Harshini
https://docs.ifs.com/techdocs/22r2/070_remote_deploy/030_patching_system/100_solution_set/#installer_handling_of_solutionsetyaml_for_middle_tierAs mentioned in this page:you can update the solution set file and trigger a delivery build: Adding or modifying a solution set must be done as a delivery. Such delivery might only contain the solutionset.yaml file as input, but it will generate an install.tem for redeploy of all clients and projections. Can u trigger a delivery build and see?
@aNm were you able to solve the issue, if so please mark as answered then this information will help to someone else as well.
Hi @ZTC ZTC JGOTA You can simple download the Developer Studio tool from https://developer.ifs.com/tools/devstudio and install into you local machine. Unlike in Apps10 you don't need to run developer studio via Citrix. Since you are in IFS Cloud 22r2, the source code is now separated., you need to download the source code from Jfrog Antifactory as well as solution repository and feed it into developer studio to configure you project in the tool. Please refer to following page in 22R2 techdoc to get more info on how to setup the project in order to get started.https://docs.ifs.com/techdocs/22r2/020_lifecycle/030_customer_solution_development/020_developing-with-devstudio/#setting_up_the_local_development_environment /Harshini
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
