Organizations are increasingly realizing that successful data analytics and artificial intelligence (AI) initiatives rely heavily on cloud infrastructure, marking cloud migration as a critical foundation for effective data strategies and AI innovations. The digital landscape now necessitates an integrated approach where data, AI, and cloud strategies work together synergistically, enhancing each other’s effectiveness and competitiveness in a data-driven economy. Chetan Mathur, CEO of automated cloud migration company Next Pathway, shares an article on Forbes explaining why cloud migration is essential for data and AI strategies for business success.

Mathur first explains how effective AI strategies require robust data management, as high-quality data is essential for AI’s machine learning processes. The data preparation tools market is projected to grow significantly, indicating that optimized data strategy is vital to AI success. Furthermore, modern cloud infrastructure is necessary for scaling and managing AI-ready data, and the global cloud migration services market is expected to expand dramatically. Quick migration from legacy systems to the cloud is crucial for organizations to harness internal and external data for AI applications.

Cloud platforms provide the computational power needed for AI, facilitating the training of complex models and processing large datasets without substantial upfront investment. Successful cloud migrations, such as Airbnb’s transition to AWS, demonstrate the advantages of cloud-based operations for improved performance and scalability.

Additionally, Mathur adds that cloud migration helps eliminate data silos, allowing for unified data access and promoting data-driven decision-making across organizations. New data strategies like distributed data meshes are becoming feasible thanks to cloud infrastructure. With over 95% of new digital workloads expected on cloud-native platforms by 2024, organizations must recognize the importance of aligning cloud migration, data strategies, and AI initiatives to remain competitive.

As the gap between digital leaders and laggards grows, businesses adopting this holistic approach can enhance innovation, efficiency, and competitive edge in the evolving digital landscape. The urgency for action is paramount for organizations looking to thrive in the future.

 

For Full Article, Click Here

Recent updates for Infor Lawson S3 mainly focus on cloud migration and release schedules for on-premises and single-tenant customers. Notably, starting in 2024, Lawson’s V10 products will follow a new release schedule, with updates in April and October instead of March and September as in previous years. Additionally, annual maintenance service packages (MSPs) will be aligned with the October release, ensuring consistent delivery of security patches, compliance updates, and bug fixes throughout the year.

For organizations still on the S3 platform, there is growing momentum towards cloud migration as Infor promotes its cloud-based ERP solutions, enhancing flexibility, scalability, and data management. Financial and other sector-specific modules for Infor Lawson S3 are increasingly being optimized for cloud use, encouraging businesses to explore cloud adoption for better integration and efficiency.

These changes reflect Infor’s commitment to modernizing its platforms and aligning with evolving cloud standards, improving both the user experience and system performance.

Migrating Lawson S3 to the Infor Cloud with Nogalis offers several advantages. Nogalis specializes in seamless migration processes, ensuring minimal downtime and operational disruptions while optimizing Lawson for the cloud environment. Our team of experts can handle complex integrations and customizations, allowing businesses to leverage Infor Cloud’s advanced features, scalability, and security. With ongoing support and proactive management, Nogalis helps organizations achieve cost savings by reducing the need for on-premise hardware and maintenance, while improving system performance and accessibility across various devices.  And once the move to the cloud is complete, Nogalis can stay on board to provide managed services for all your Infor Cloud products.  Here is some more information about our Managed Service and Project offerings.

When it is time to move to the cloud, Archiving Lawson data using APIX will be crucial. APIX offers a reliable and compliant data archiving solution, allowing businesses to securely store historical Lawson data without burdening the cloud environment.  Additionally, APIX provides a sleek UI that puts historical data at users’ fingertips. Proper archiving helps maintain data integrity and ensures easy access to legacy information for auditing and reporting needs. By archiving Lawson data before migration, businesses can streamline the transition, reduce storage costs in the cloud, and comply with regulatory requirements, all while ensuring that critical data is preserved and accessible post-migration.  Book a demo here!

As cloud adoption increases and becomes the more prominent business solution, there is still a lot of confusion and hesitation about moving to the cloud. Industry expert David S. Linthicum shares an article on InfoWorld.com discussing the ongoing confusion and challenges surrounding cloud security. The article highlights several factors contributing to this confusion, including the evolving nature of cloud technologies, the shared responsibility model wherein cloud providers and customers both have roles in securing data, and a lack of clear communication and understanding among stakeholders. Linthicum explains simply that when it comes to cloud security, prioritization is key. “It is vital to prioritize vulnerability remediation, particularly for areas at high risk. Regular audits and proactive patching can minimize exposure and enhance security resilience,” he states. “Organizations can better protect their cloud infrastructures and safeguard their data assets by evolving from reactive measures to a sustainable security framework, but how the heck do you do this?” Below, Linthicum highlights key areas to prioritize for cloud security to run successfully within your business.

  • Implement strong access control measures. Regularly audit and review access keys to ensure they are necessary and have the appropriate permission level. Rotate access keys frequently and eliminate unused or unnecessary keys to minimize the risk of unauthorized access.
  • Enhance identity and access management (IAM). Implement stringent IAM policies that enforce the principle of least privilege. Utilize role-based access controls (RBAC) to ensure that users only have access to the resources they need to perform their job functions.
  • Conduct regular security audits and penetration testing. Examine cloud environments to identify and address vulnerabilities and misconfigurations before attackers can exploit them. I recommend springing for outside organizations that specialize in this stuff instead of using your own security team. I don’t know how often I have done a post-mortem on a breach and discovered that they have been grading themselves for years. Guess what? They gave themselves an A, and even had that tied to bonuses.
  • Deploy automated monitoring and response systems. Automated tools provide continuous monitoring and real-time threat detection. Implement systems that can automatically respond to certain types of security incidents to minimize the time between detection and remediation.
  • Implement Kubernetes best practices. Ensure that Kubernetes API servers are not publicly accessible unless necessary, and limit user permissions to reduce potential attack vectors.
  • Prioritize vulnerability management. Regularly update and patch all software and cloud services, especially those with high vulnerability priority ratings, to protect against newly discovered weaknesses.
  • Strengthen governance, risk, and compliance (GRC) frameworks. Continually develop and maintain robust GRC practices to assess and improve the effectiveness of security controls. This should include policy development, risk assessment, compliance tracking, and continuous improvement initiatives.
  • Train staff on security awareness. Provide ongoing training and awareness programs for all employees to ensure they understand current threats and best practices for maintaining security within cloud environments. As I’ve stated before, most cloud computing security problems are breathing—people are the key here.

While cloud security can be complex, proactive engagement and informed decision-making can lead to better security outcomes.

 

For Full Article, Click Here

Infor recently announced that the Infor Cloverleaf Data Integration Platform is now interoperable with the NVIDIA’s Holoscan AI platform, with the aim at enhancing medical devices with cutting-edge AI and deep learning technologies. Infor Cloverleaf helps medical device customers integrate and share healthcare data across different systems and platforms, such as electronic health records and medical devices. Per the press release, pairing this with NVIDIA Holoscan allows customers to harness high-quality data to feed into AI models efficiently. In addition, medical device customers can leverage NVIDIA Holoscan’s real-time AI capabilities to build agents and applications that assist clinicians by providing real time insights that can be leveraged pre, intra, and post procedure. By connecting this real-time processing power with the Cloverleaf interoperability engine, the AI agents can access up-to-date patient data, imaging, and vitals in real time, making more precise recommendations. Infor Cloverleaf has been widely adopted across hospitals and medical research facilities worldwide. Its continual top-tier rankings in this analyst report underscore its unmatched value in secure and compliant data interoperability, which is critical for managing the vast amounts of data essential in AI applications. Furthermore, the integration of Cloverleaf with NVIDIA Holoscan will enable developers to build powerful sensor processing AI applications that can easily integrate with EHR systems to leverage patient-specific data, with the goal of improving patient outcomes, enhancing surgical procedures, and reducing administrative burdens.

 

For Full Article, Click Here

When installing Infor Process Designer, a new addition for install is that it is now asking for the Java 17 path.  To complete the install, you will first have to download JDK 17 from Amazon Corretto and install it. Then verify that the install path is added to JAVA_HOME and Path environment variables.

 

Next, run the IPD installer and choose New Install.  Select the directory to install IPD. Browse to the Java 17 location if it isn’t already populated.

 

The option to copy configuration information is now available.  You can select “Yes” here and select the existing IPD configuration to copy.

 

Click Next and Install

 

Many businesses are transitioning to new enterprise resource planning (ERP) systems, whether to upgrade their current ones, move over to the cloud, or feel the need for change. The go-live phase is when everything in your ERP project comes to fruition – and the success of this stage makes or breaks your new system. ERP experts at Synavos share a guide on Medium.com on how to have a successful go-live and how to prepare for this transformative step.

  1. Pre-Go-Live Preparations. “Preparation is key for a smooth ERP Go-Live. Before your launch date, you should have comprehensive testing, user training, and data migration strategies in place. This phase involves finalizing configurations, conducting user acceptance testing (UAT), and ensuring that everyone involved understands their roles.”
  2. Train Your Team for Success. “Your team is your greatest asset, and their proper training is crucial for a successful Go-Live. Investing in user training can significantly impact how well your team adapts to the new ERP system.”
  3. Data Migration Strategies. “Data integrity is vital during your ERP Go-Live. Effective data migration ensures that your new system has accurate, up-to-date information from the outset.”
  4. Communication Is Key. “Effective communication throughout the Go-Live process cannot be overstated. Keeping all stakeholders informed about timelines, expectations, and any potential disruptions will go a long way.”
  5. Go-Live Day: What to Expect. “On Go-Live day, emotions run high, and it’s natural to feel a mix of excitement and anxiety. Have a clear plan in place for the day, including a checklist of tasks and a designated support team ready to troubleshoot any issues.”
  6. Post-Go-Live Support and Monitoring. “Once the dust settles, the real work begins. Monitoring system performance and user feedback closely after your ERP Go-Live is critical.”

As you finalize your plans for ERP Go-Live, Synavos wants us to remember that this phase is the beginning of a new chapter for your organization. Each step you take now contributes to a stronger, more efficient future.

 

For Full Article, Click Here

Problem: The GL40.2 form is not sized right.

Can you please open again program in Lawson Portal and once you open it, please do “CTRL+ALT+A” from your keyboard and send me the result it will show the XML file.

<?xml version=”1.0″ encoding=”ISO-8859-1″?><form FORMTYPE=”window” NOTKNXFER=”1″ RUNTYPE=”lapm” SYSTEM=”GL” TITLE=”Define Journal” TOKEN=”GL40.2″ TYPE=”ONLINE” XMLGenBy=”xscrgen 9.0.1.8.221 2011-01-28 04:00:00 (201105)” XMLGenDT=”20120205 2237″ add=”A” chg=”C” custom=”1″ datareq=”ACR” dateupgrade=”1445006844693″ dblXmit=”D” defaultFC=”” defaultui=”false” del=”D” evttype=”” formid=”GL40.2_CUSTOM” gHeight=”24″ gWidth=”13″ height=”24″ hiddenFC=”0″ id=”form1″ inq=”I” keycheck=”CDRB” lineDupAllow=”0″ nbr=”form1″ next=”NP” objmode=”0″ pdl=”DEVRY” prefc=”” rtntype=”ALL” scr=”GI” staticsize=”1″ targetid=”junk” typ=”o” width=”80″ workflow=”0″ rootdir=”/lawson/portal” mode=”modal” hkey=”” host=”portal” allowListMode=”1″ iosVersion=”10.0.” allowTransfer=”0″ allowManualCF=”0″>
<transfers id=”transfers1″ nbr=”_l1″/>
<fld al=”right” col=”17″ id=”label1″ nbr=”_l2″ nm=”Company:” row=”2″ sz=”8″ tp=”label”/>
<fld al=”right” col=”12″ id=”label2″ nbr=”_l3″ nm=”Year, Period:” row=”3″ sz=”13″ tp=”label”/>
<fld al=”right” col=”18″ id=”label3″ nbr=”_l4″ nm=”System:” row=”4″ sz=”7″ tp=”label”/>
<fld al=”right” col=”1″ id=”label4″ nbr=”_l5″ nm=”Type, Journal, Sequence:” row=”5″ sz=”24″ tp=”label”/>
<fld al=”left” blankzero=”0″ drlnokeys=”0″ ed=”upper” hdet=”1″ hsel=”1″ id=”hidden1″ nbr=”_f0″ nm=”TC” req=”1″ sz=”6″ tp=”Hidden”/>
<toolbar al=”left” blankzero=”1″ col=”1″ drlnokeys=”0″ ed=”upper” hdet=”1″ hsel=”1″ id=”toolbar1″ nbr=”_f1″ nm=”FC” req=”1″ row=”0″ sz=”1″>
<button Disp=”A” id=”button1″ nbr=”_l6″ nm=”Add” value=”A” visible=”1″/>
<button Disp=”C” id=”button2″ nbr=”_l7″ nm=”Change” value=”C” visible=”1″/>
<button Disp=”D” id=”button3″ nbr=”_l8″ nm=”Delete” value=”D” visible=”1″/>
<button Disp=”I” id=”button4″ nbr=”_l9″ nm=”Inquire” value=”I” visible=”1″/>
<button Disp=”N” id=”button5″ nbr=”_l10″ nm=”Next” value=”N” visible=”1″/>
<button Disp=”P” id=”button6″ nbr=”_l11″ nm=”Previous” value=”P” visible=”1″/>
<button Disp=”R” id=”button7″ nbr=”_l12″ nm=”Release” value=”R” visible=”0″/>
<button Disp=”B” id=”button8″ nbr=”_l13″ nm=”BaseZoneChange” value=”B” visible=”0″/>
</toolbar>
<fld al=”left” blankzero=”0″ drlnokeys=”0″ ed=”numeric” hdet=”1″ id=”hidden2″ nbr=”_f2″ nm=”PT-XMIT-NBR” sz=”1″ tp=”Hidden”/>
<fld al=”left” blankzero=”0″ drlnokeys=”0″ ed=”upper” hdet=”1″ id=”hidden3″ keynbr=”GFI” nbr=”_f3″ nm=”PT-MIMIC-ENTRY” sz=”1″ tp=”Hidden”/>
<fld al=”left” blankzero=”0″ decsz=”2″ drlnokeys=”0″ ed=”signed” hdet=”1″ id=”hidden4″ keynbr=”GkI” mxsz=”20″ nbr=”_f4″ nknimp=”1″ nm=”GLC-ENTRY-DB” sz=”17″ tp=”Hidden”/>
<fld al=”left” blankzero=”0″ decsz=”2″ drlnokeys=”0″ ed=”signed” hdet=”1″ id=”hidden5″ keynbr=”GkH” mxsz=”20″ nbr=”_f5″ nknimp=”1″ nm=”GLC-ENTRY-CR” sz=”17″ tp=”Hidden”/>
<fld al=”left” blankzero=”0″ decsz=”2″ drlnokeys=”0″ ed=”signed” hdet=”1″ id=”hidden6″ keynbr=”GkC” mxsz=”20″ nbr=”_f6″ nknimp=”1″ nm=”ENTRY-DIFF” sz=”17″ tp=”Hidden”/>
<fld al=”left” blankzero=”0″ decsz=”2″ drlnokeys=”0″ ed=”signed” hdet=”1″ id=”hidden7″ keynbr=”GkK” mxsz=”17″ nbr=”_f7″ nknimp=”1″ nm=”GLC-UNIT-ENTRY-DB” sz=”14″ tp=”Hidden”/>
<fld al=”left” blankzero=”0″ decsz=”2″ drlnokeys=”0″ ed=”signed” hdet=”1″ id=”hidden8″ keynbr=”GkJ” mxsz=”17″ nbr=”_f8″ nknimp=”1″ nm=”GLC-UNIT-ENTRY-CR” sz=”14″ tp=”Hidden”/>
<fld al=”left” blankzero=”0″ decsz=”2″ drlnokeys=”0″ ed=”signed” hdet=”1″ id=”hidden9″ keynbr=”GkL” mxsz=”17″ nbr=”_f9″ nknimp=”1″ nm=”UNIT-ENTRY-DIFF” sz=”14″ tp=”Hidden”/>
<fld al=”left” blankzero=”0″ decsz=”2″ drlnokeys=”0″ ed=”signed” hdet=”1″ id=”hidden10″ keynbr=”GkE” mxsz=”20″ nbr=”_f10″ nknimp=”1″ nm=”GLC-BASE-AUTO-DB” sz=”17″ tp=”Hidden”/>
<fld al=”left” blankzero=”0″ decsz=”2″ drlnokeys=”0″ ed=”signed” hdet=”1″ id=”hidden11″ keynbr=”GkD” mxsz=”20″ nbr=”_f11″ nknimp=”1″ nm=”GLC-BASE-AUTO-CR” sz=”17″ tp=”Hidden”/>
<fld al=”left” blankzero=”0″ decsz=”2″ drlnokeys=”0″ ed=”signed” hdet=”1″ id=”hidden12″ keynbr=”GkA” mxsz=”20″ nbr=”_f12″ nknimp=”1″ nm=”BASE-AUTO-DIFF” sz=”17″ tp=”Hidden”/>
<fld al=”left” blankzero=”0″ decsz=”2″ drlnokeys=”0″ ed=”signed” hdet=”1″ id=”hidden13″ keynbr=”GkG” mxsz=”20″ nbr=”_f13″ nknimp=”1″ nm=”GLC-BASE-DEBITS” sz=”17″ tp=”Hidden”/>
<fld al=”left” blankzero=”0″ decsz=”2″ drlnokeys=”0″ ed=”signed” hdet=”1″ id=”hidden14″ keynbr=”GkF” mxsz=”20″ nbr=”_f14″ nknimp=”1″ nm=”GLC-BASE-CREDITS” sz=”17″ tp=”Hidden”/>
<fld al=”left” blankzero=”0″ decsz=”2″ drlnokeys=”0″ ed=”signed” hdet=”1″ id=”hidden15″ keynbr=”GkB” mxsz=”20″ nbr=”_f15″ nknimp=”1″ nm=”BASE-DIFF” sz=”17″ tp=”Hidden”/>
<fld al=”left” blankzero=”0″ drlnokeys=”0″ ed=”upper” hdet=”1″ id=”hidden16″ keynbr=”26″ nbr=”_f16″ nm=”CALLED-PROGRAM” sz=”5″ tp=”Hidden”/>
<fld al=”right” blankzero=”1″ col=”26″ deftkn=”GL10.1″ drlnokeys=”1″ ed=”numeric” hdef=”1″ hdet=”1″ hrul=”1″ hsel=”1″ hselrul=”1″ id=”text1″ key=”1″ keynbr=”01″ label=”Company:” nbr=”_f17″ nextreq=”1″ nm=”GLC-COMPANY” req=”1″ row=”2″ sz=”4″ tp=”Text”/>
<fld al=”left” blankzero=”0″ deftkn=”CU01.1″ drlnokeys=”0″ ed=”upper” hdef=”1″ hdet=”1″ hrul=”1″ hsel=”1″ hselrul=”1″ id=”hidden17″ keynbr=”GC” nbr=”_f18″ nm=”GLS-CURRENCY-CODE” sz=”5″ tp=”Hidden”/>
<fld al=”left” blankzero=”1″ col=”41″ drlnokeys=”0″ hdet=”1″ id=”out1″ keynbr=”01D” nbr=”_f19″ nm=”GLS-NAME” row=”2″ sz=”30″ tp=”Out”/>
<fld al=”right” blankzero=”1″ col=”26″ drlnokeys=”0″ ed=”numeric” hdet=”1″ id=”text2″ key=”1″ keynbr=”06″ label=”Year, Period:” nbr=”_f20″ nm=”GLC-FISCAL-YEAR” row=”3″ sz=”4″ tp=”Text”/>
<fld al=”right” blankzero=”1″ col=”31″ drlnokeys=”0″ ed=”numeric” hdet=”1″ hsel=”1″ id=”select1″ key=”1″ keynbr=”GP” nbr=”_f21″ nm=”GLC-ACCT-PERIOD” row=”3″ seltype=”” sz=”2″ tp=”Select”>
<vals Disp=”01:13″ Tran=”01:13″ id=”vals1″ nbr=”_l14″>01:13</vals>
</fld>
<fld al=”left” blankzero=”1″ col=”26″ deftkn=”GL01.1″ defval=”GL” drlnokeys=”0″ ed=”upper” hdef=”1″ hdet=”1″ hrul=”1″ hsel=”1″ hselrul=”1″ id=”text3″ key=”1″ keynbr=”GS” label=”System:” nbr=”_f22″ nm=”GLC-SYSTEM” req=”1″ row=”4″ sz=”2″ tp=”Text”/>
<fld al=”left” blankzero=”1″ col=”41″ drlnokeys=”0″ hdet=”1″ id=”out2″ keynbr=”G6Y” nbr=”_f23″ nm=”GCD-DESCRIPTION” row=”4″ sz=”30″ tp=”Out”/>
<fld al=”left” blankzero=”1″ col=”26″ defval=”N” drlnokeys=”0″ ed=”upper” hdet=”1″ hsel=”1″ id=”select2″ key=”1″ keynbr=”GK” label=”Type, Journal, Sequence:” nbr=”_f24″ nm=”GLC-JE-TYPE” req=”1″ row=”5″ seltype=”” sz=”1″ tp=”Select”>
<vals Disp=”N” Tran=”N” id=”vals2″ nbr=”_l15″>Normal</vals>
<vals Disp=”I” Tran=”I” id=”vals3″ nbr=”_l16″>Intercompany</vals>
</fld>
<fld al=”right” att_comment=”1″ att_url=”1″ blankzero=”1″ col=”28″ deftkn=”GL40.1″ drlnokeys=”0″ ed=”numeric” hdef=”1″ hdet=”1″ hrul=”1″ hsel=”1″ hselrul=”1″ id=”text4″ key=”1″ keynbr=”GI” nbr=”_f25″ nm=”GLC-CONTROL-GROUP” row=”5″ sz=”8″ tp=”Text”/>
<fld al=”right” blankzero=”1″ col=”37″ drlnokeys=”0″ ed=”numeric” hdet=”1″ id=”text5″ key=”1″ keynbr=”GIS” nbr=”_f26″ nm=”GLC-JE-SEQUENCE” row=”5″ sz=”2″ tp=”Text”/>
<fld al=”left” blankzero=”1″ col=”41″ drlnokeys=”0″ hdet=”1″ id=”text6″ keynbr=”GID” nbr=”_f27″ nm=”GLC-DESCRIPTION” req=”1″ row=”5″ sz=”30″ tp=”Text”/>
<tabregion col=”1″ det=”0″ folders=”1″ grp=”tab1″ height=”11″ id=”tabregion1″ nbr=”TR0″ row=”6″ scroll=”0″ width=”79″>
<tab id=”tab1″ nbr=”TF0-0″ nm=” Main” par=”TR0″ secnm=”PRIMARY-TAB” tabprot=”0″>
<fld al=”right” col=”17″ id=”label5″ nbr=”_l17″ nm=”User Analysis:” par=”TF0-0″ row=”0″ sz=”14″ tp=”label”/>
<fld al=”right” col=”19″ id=”label6″ nbr=”_l18″ nm=”Source Code:” par=”TF0-0″ row=”1″ sz=”12″ tp=”label”/>
<fld al=”right” col=”11″ id=”label7″ nbr=”_l19″ nm=”Description Default:” par=”TF0-0″ row=”2″ sz=”20″ tp=”label”/>
<fld al=”right” col=”21″ id=”label8″ nbr=”_l20″ nm=”Reference:” par=”TF0-0″ row=”3″ sz=”10″ tp=”label”/>
<fld al=”right” col=”21″ id=”label9″ nbr=”_l21″ nm=”Hold Code:” par=”TF0-0″ row=”4″ sz=”10″ tp=”label”/>
<fld al=”right” col=”5″ id=”label10″ nbr=”_l22″ nm=”Automatic Reverse, Period:” par=”TF0-0″ row=”5″ sz=”26″ tp=”label”/>
<fld al=”right” col=”21″ id=”label11″ nbr=”_l23″ nm=”Base Zone:” par=”TF0-0″ row=”6″ sz=”10″ tp=”label”/>
<fld al=”right” col=”15″ id=”label12″ nbr=”_l24″ nm=”Document Number:” par=”TF0-0″ row=”7″ sz=”16″ tp=”label”/>
<fld al=”right” col=”18″ id=”label13″ nbr=”_l25″ nm=”Journal Book:” par=”TF0-0″ row=”8″ sz=”13″ tp=”label”/>
<fld al=”right” col=”2″ id=”label14″ nbr=”_l26″ nm=”Journal Book Sequence Number:” par=”TF0-0″ row=”9″ sz=”29″ tp=”label”/>
<fld al=”left” blankzero=”1″ drlnokeys=”0″ ed=”upper” hdet=”1″ id=”tabfld1″ nbr=”_f28″ nm=”PRIMARY-TAB” par=”TF0-0″ sz=”17″ tp=”Tab”/>
<fld al=”left” blankzero=”1″ col=”32″ drlnokeys=”0″ ed=”upper” hdef=”1″ hdet=”1″ id=”text7″ keynbr=”SB2″ label=”User Analysis:” mxsz=”103″ nbr=”_f29″ nm=”GLC-SEGMENT-BLOCK” par=”TF0-0″ row=”0″ sz=”41″ tp=”Text”/>
<fld ALT_REF=”_f55″ al=”left” ar=”1″ blankzero=”1″ col=”32″ deftkn=”GL05.1″ defval=”JE” drlnokeys=”0″ ed=”upper” hdef=”1″ hdet=”1″ hrul=”1″ hsel=”1″ hselrul=”1″ id=”text8″ keynbr=”GCS” label=”Source Code:” nbr=”_f30″ nm=”GLC-SOURCE-CODE” par=”TF0-0″ row=”1″ sz=”2″ tp=”Text”/>
<fld ALT_REF=”_f56″ al=”left” ar=”1″ blankzero=”1″ col=”44″ drlnokeys=”0″ hdet=”1″ id=”out3″ keynbr=”GCT” nbr=”_f31″ nm=”GLC-SOURCE-CODE-DESC” par=”TF0-0″ row=”1″ sz=”30″ tp=”Out”/>
<fld al=”left” blankzero=”1″ col=”32″ defval=”J” drlnokeys=”0″ ed=”upper” hdet=”1″ hsel=”1″ id=”select3″ label=”Description Default:” nbr=”_f32″ nm=”GLC-TRAN-DESC-DFLT” par=”TF0-0″ row=”2″ seltype=”” sz=”1″ tp=”Select”>
<vals Disp=”J” Tran=”J” id=”vals4″ nbr=”_l27″>Journal Header</vals>
<vals Disp=”P” Tran=”P” id=”vals5″ nbr=”_l28″>Prior Transaction Line</vals>
</fld>
<fld al=”left” blankzero=”1″ col=”44″ defval=”_f32″ drlnokeys=”0″ hdet=”1″ id=”out4″ isxlt=”_f32″ nbr=”_f33″ nm=”GLC-TRAN-DESC-DFLT” par=”TF0-0″ row=”2″ sz=”30″ tp=”Out”/>
<fld al=”left” blankzero=”1″ col=”32″ drlnokeys=”0″ hdet=”1″ id=”text9″ keynbr=”GkX” label=”Reference:” nbr=”_f34″ nm=”GLC-REFERENCE” par=”TF0-0″ row=”3″ sz=”10″ tp=”Text”/>
<fld al=”left” blankzero=”1″ col=”32″ deftkn=”GL12.1″ drlnokeys=”0″ ed=”upper” hdef=”1″ hdet=”1″ hsel=”1″ hselrul=”1″ id=”text10″ keynbr=”HLC” label=”Hold Code:” nbr=”_f35″ nm=”GLC-HOLD-CODE” par=”TF0-0″ row=”4″ sz=”4″ tp=”Text”/>
<fld al=”left” blankzero=”1″ col=”44″ drlnokeys=”0″ hdet=”1″ id=”out5″ nbr=”_f36″ nm=”GLC-HOLD-CODE-DESC” par=”TF0-0″ row=”4″ sz=”30″ tp=”Out”/>
<fld al=”left” blankzero=”1″ col=”32″ defval=”N” drlnokeys=”0″ ed=”upper” hdet=”1″ hsel=”1″ id=”select4″ keynbr=”GkM” label=”Automatic Reverse, Period:” nbr=”_f37″ nknimp=”1″ nm=”GLC-AUTO-REV” par=”TF0-0″ row=”5″ seltype=”” sz=”1″ tp=”Select”>
<vals Disp=”N” Tran=”N” id=”vals6″ nbr=”_l29″>No</vals>
<vals Disp=”Y” Tran=”Y” id=”vals7″ nbr=”_l30″>Yes</vals>
</fld>
<fld al=”left” blankzero=”1″ col=”35″ drlnokeys=”0″ ed=”numeric” hdet=”1″ hsel=”1″ id=”select5″ keynbr=”G1b” nbr=”_f38″ nknimp=”1″ nm=”GLC-AUTO-REV-PD” par=”TF0-0″ row=”5″ seltype=”” sz=”2″ tp=”Select”>
<vals Disp=”00″ Tran=”00″ id=”vals8″ nbr=”_l31″>Next Period</vals>
<vals Disp=”01″ Tran=”01″ id=”vals9″ nbr=”_l32″>Period 1</vals>
<vals Disp=”02″ Tran=”02″ id=”vals10″ nbr=”_l33″>Period 2</vals>
<vals Disp=”03″ Tran=”03″ id=”vals11″ nbr=”_l34″>Period 3</vals>
<vals Disp=”04″ Tran=”04″ id=”vals12″ nbr=”_l35″>Period 4</vals>
<vals Disp=”05″ Tran=”05″ id=”vals13″ nbr=”_l36″>Period 5</vals>
<vals Disp=”06″ Tran=”06″ id=”vals14″ nbr=”_l37″>Period 6</vals>
<vals Disp=”07″ Tran=”07″ id=”vals15″ nbr=”_l38″>Period 7</vals>
<vals Disp=”08″ Tran=”08″ id=”vals16″ nbr=”_l39″>Period 8</vals>
<vals Disp=”09″ Tran=”09″ id=”vals17″ nbr=”_l40″>Period 9</vals>
<vals Disp=”10″ Tran=”10″ id=”vals18″ nbr=”_l41″>Period 10</vals>
<vals Disp=”11″ Tran=”11″ id=”vals19″ nbr=”_l42″>Period 11</vals>
<vals Disp=”12″ Tran=”12″ id=”vals20″ nbr=”_l43″>Period 12</vals>
<vals Disp=”13″ Tran=”13″ id=”vals21″ nbr=”_l44″>Period 13</vals>
</fld>
<fld al=”left” blankzero=”1″ col=”44″ defval=”_f37″ drlnokeys=”0″ hdet=”1″ id=”out6″ isxlt=”_f37″ mxsz=”4″ nbr=”_f39″ nm=”GLC-AUTO-REV” par=”TF0-0″ row=”5″ sz=”3″ tp=”Out”/>
<fld al=”left” blankzero=”1″ col=”49″ defval=”_f38″ drlnokeys=”0″ hdet=”1″ id=”out7″ isxlt=”_f38″ nbr=”_f40″ nm=”GLC-AUTO-REV-PD” par=”TF0-0″ row=”5″ sz=”20″ tp=”Out”/>
<fld al=”right” blankzero=”1″ col=”32″ deftkn=”GL30.1″ drlnokeys=”0″ ed=”numeric” hdef=”1″ hdet=”1″ hsel=”1″ hselrul=”1″ id=”text11″ keynbr=”LZ” label=”Base Zone:” nbr=”_f41″ nm=”GLC-BASE-ZONE” par=”TF0-0″ row=”6″ sz=”15″ tp=”Text”/>
<fld al=”left” blankzero=”1″ col=”32″ drlnokeys=”0″ ed=”upper” hdet=”1″ id=”text12″ label=”Document Number:” nbr=”_f42″ nm=”GLC-DOCUMENT-NBR” par=”TF0-0″ row=”7″ sz=”27″ tp=”Text”/>
<fld al=”left” blankzero=”1″ col=”32″ deftkn=”JB00.1″ drlnokeys=”0″ ed=”upper” hdef=”1″ hdet=”1″ hrul=”1″ hsel=”1″ hselrul=”1″ id=”text13″ keynbr=”JBN” label=”Journal Book:” nbr=”_f43″ nm=”GLC-JRNL-BOOK-NBR” par=”TF0-0″ row=”8″ sz=”12″ tp=”Text”/>
<fld al=”left” blankzero=”1″ col=”46″ drlnokeys=”0″ hdet=”1″ id=”out8″ keynbr=”JBD” nbr=”_f44″ nm=”JBK-DESCRIPTION” par=”TF0-0″ row=”8″ sz=”30″ tp=”Out”/>
<fld al=”right” blankzero=”1″ col=”32″ drlnokeys=”0″ ed=”numeric” hdet=”1″ id=”out9″ keynbr=”JBS” label=”Journal Book Sequence Number:” nbr=”_f45″ nm=”GLC-JBK-SEQ-NBR” par=”TF0-0″ row=”9″ sz=”10″ tp=”Out”/>
<push al=”center” blankzero=”0″ btnnm=” Copy” col=”28″ hdef=”1″ id=”push1″ keynbr=”GL40.6″ nbr=”_f46″ nm=”MIMIC-WIN” par=”TF0-0″ row=”10″ sz=”6″/>
</tab>
<tab id=”tab2″ nbr=”TF0-1″ nm=” Dates, Currency” par=”TR0″ secnm=”PERIODS-TAB” tabprot=”0″>
<fld col=”3″ height=”5″ id=”rect1″ nbr=”_l45″ nm=” Dates ” par=”TF0-1″ row=”0″ tp=”rect” width=”68″/>
<fld col=”3″ height=”4″ id=”rect2″ nbr=”_l46″ nm=” Currency ” par=”TF0-1″ row=”5″ tp=”rect” width=”68″/>
<fld al=”right” col=”14″ id=”label15″ nbr=”_l47″ nm=”Posting:” par=”TF0-1″ row=”1″ sz=”8″ tp=”label”/>
<fld al=”right” col=”10″ id=”label16″ nbr=”_l48″ nm=”Transaction:” par=”TF0-1″ row=”2″ sz=”12″ tp=”label”/>
<fld al=”right” col=”8″ id=”label17″ nbr=”_l49″ nm=”ADB Effective:” par=”TF0-1″ row=”3″ sz=”14″ tp=”label”/>
<fld al=”right” col=”8″ id=”label18″ nbr=”_l50″ nm=”Currency Code:” par=”TF0-1″ row=”6″ sz=”14″ tp=”label”/>
<fld al=”right” col=”8″ id=”label19″ nbr=”_l51″ nm=”Exchange Rate:” par=”TF0-1″ row=”7″ sz=”14″ tp=”label”/>
<fld al=”left” blankzero=”1″ drlnokeys=”0″ ed=”upper” hdet=”1″ id=”tabfld2″ nbr=”_f47″ nm=”PERIODS-TAB” par=”TF0-1″ sz=”17″ tp=”Tab”/>
<fld al=”left” blankzero=”1″ col=”23″ drlnokeys=”0″ ed=”date” hdet=”1″ id=”text14″ keynbr=”Y59″ label=”Posting:” nbr=”_f48″ nm=”GLC-POSTING-DATE” par=”TF0-1″ row=”1″ sz=”6″ tp=”Text”/>
<fld al=”left” blankzero=”1″ col=”23″ defval=”CTD” drlnokeys=”0″ ed=”date” hdet=”1″ id=”text15″ label=”Transaction:” nbr=”_f49″ nm=”GLC-DATE” par=”TF0-1″ row=”2″ sz=”6″ tp=”Text”/>
<fld al=”left” blankzero=”1″ col=”23″ drlnokeys=”0″ ed=”date” hdet=”1″ id=”text16″ keynbr=”TTE” label=”ADB Effective:” nbr=”_f50″ nm=”GLC-EFFECT-DATE” par=”TF0-1″ row=”3″ sz=”6″ tp=”Text”/>
<fld al=”left” blankzero=”1″ btnnm=”98″ col=”23″ deftkn=”CU01.1″ drlnokeys=”0″ ed=”upper” hdef=”1″ hdet=”1″ hrul=”1″ hsel=”1″ hselrul=”1″ id=”text17″ keynbr=”JC” label=”Currency Code:” nbr=”_f51″ nknimp=”1″ nm=”GLC-CURRENCY-CODE” par=”TF0-1″ row=”6″ sz=”5″ tp=”Text”/>
<fld al=”left” blankzero=”1″ col=”37″ drlnokeys=”0″ hdet=”1″ id=”out10″ keynbr=”98D” nbr=”_f52″ nm=”CUC-DESCRIPTION” par=”TF0-1″ row=”6″ sz=”30″ tp=”Out”/>
<fld al=”right” blankzero=”1″ col=”23″ decsz=”7″ deftkn=”CU10.1″ drlnokeys=”0″ ed=”numeric” hdef=”1″ hdet=”1″ hsel=”1″ hselrul=”1″ id=”text18″ keynbr=”98R” label=”Exchange Rate:” nbr=”_f53″ nknimp=”1″ nm=”GLC-BASERATE” par=”TF0-1″ row=”7″ sz=”15″ tp=”Text”/>
</tab>
<tab id=”tab3″ nbr=”TF0-2″ nm=” Attributes” par=”TR0″ secnm=”ATTRIB-TAB” tabprot=”0″>
<fld al=”right” col=”9″ id=”label20″ nbr=”_l52″ nm=”Source Code:” par=”TF0-2″ row=”1″ sz=”12″ tp=”label”/>
<fld al=”left” blankzero=”1″ drlnokeys=”0″ ed=”upper” hdet=”1″ id=”tabfld3″ mxsz=”17″ nbr=”_f54″ nm=”ATTRIB-TAB” par=”TF0-2″ sz=”14″ tp=”Tab”/>
<fld ALT_REF=”_f30″ al=”left” ar=”1″ blankzero=”1″ col=”22″ deftkn=”GL05.1″ defval=”JE” drlnokeys=”0″ ed=”upper” hdef=”1″ hdet=”1″ hrul=”1″ hsel=”1″ hselrul=”1″ id=”text19″ keynbr=”GCS” label=”Source Code:” nbr=”_f55″ nm=”GLC-SOURCE-CODE” par=”TF0-2″ row=”1″ sz=”2″ tp=”Text”/>
<fld ALT_REF=”_f31″ al=”left” ar=”1″ blankzero=”1″ col=”29″ drlnokeys=”0″ hdet=”1″ id=”out11″ keynbr=”GCT” nbr=”_f56″ nm=”GLC-SOURCE-CODE-DESC” par=”TF0-2″ row=”1″ sz=”30″ tp=”Out”/>
<fld al=”left” blankzero=”0″ drlnokeys=”0″ ed=”upper” hdet=”1″ id=”hidden18″ keynbr=”GXA” nbr=”_f57″ nm=”GLT-MATRIX-CAT-1″ sz=”12″ tp=”Hidden”/>
<fld al=”left” blankzero=”1″ col=”9″ drlnokeys=”0″ hdet=”1″ id=”out12″ keynbr=”GX1″ nbr=”_f58″ nm=”GLT-DESCRIPTION-1″ par=”TF0-2″ row=”3″ sz=”30″ tp=”Out”/>
<fld al=”left” blankzero=”1″ col=”41″ deftkn=”MX00.1″ drlnokeys=”0″ ed=”upper” hdef=”1″ hdet=”1″ hsel=”1″ hselrul=”1″ id=”text20″ keynbr=”CV1″ mxsz=”32″ nbr=”_f59″ nm=”GLT-MX-VALUE-1″ par=”TF0-2″ row=”3″ sz=”20″ tp=”Text”/>
<fld al=”left” blankzero=”0″ drlnokeys=”0″ ed=”upper” hdet=”1″ id=”hidden19″ keynbr=”GXB” nbr=”_f60″ nm=”GLT-MATRIX-CAT-2″ sz=”12″ tp=”Hidden”/>
<fld al=”left” blankzero=”1″ col=”9″ drlnokeys=”0″ hdet=”1″ id=”out13″ keynbr=”GX2″ nbr=”_f61″ nm=”GLT-DESCRIPTION-2″ par=”TF0-2″ row=”4″ sz=”30″ tp=”Out”/>
<fld al=”left” blankzero=”1″ col=”41″ deftkn=”MX00.1″ drlnokeys=”0″ ed=”upper” hdef=”1″ hdet=”1″ hsel=”1″ hselrul=”1″ id=”text21″ keynbr=”CV2″ mxsz=”32″ nbr=”_f62″ nm=”GLT-MX-VALUE-2″ par=”TF0-2″ row=”4″ sz=”20″ tp=”Text”/>
<fld al=”left” blankzero=”0″ drlnokeys=”0″ ed=”upper” hdet=”1″ id=”hidden20″ keynbr=”GXC” nbr=”_f63″ nm=”GLT-MATRIX-CAT-3″ sz=”12″ tp=”Hidden”/>
<fld al=”left” blankzero=”1″ col=”9″ drlnokeys=”0″ hdet=”1″ id=”out14″ keynbr=”GX3″ nbr=”_f64″ nm=”GLT-DESCRIPTION-3″ par=”TF0-2″ row=”5″ sz=”30″ tp=”Out”/>
<fld al=”left” blankzero=”1″ col=”41″ deftkn=”MX00.1″ drlnokeys=”0″ ed=”upper” hdef=”1″ hdet=”1″ hsel=”1″ hselrul=”1″ id=”text22″ keynbr=”CV3″ mxsz=”32″ nbr=”_f65″ nm=”GLT-MX-VALUE-3″ par=”TF0-2″ row=”5″ sz=”20″ tp=”Text”/>
</tab>
</tabregion>
<fld al=”left” blankzero=”0″ drlnokeys=”0″ ed=”upper” hdet=”1″ id=”sp1″ nbr=”_f66″ nm=”_HK” req=”1″ sz=”23″ tp=”Sp”/>
<PATH id=”path1″ nbr=”_l53″/>
<msgBar bMsgArea=”1″ id=”msgbar1″ nbr=”msgBar”/>
<XSCRIPT id=”script1″ nbr=”_s1″>
<![CDATA[
function FORM_OnBeforeTransaction(fc)
{
if ((fc == “D”) ||
(fc == “C”))
{

var vID = portalWnd.oUserProfile.getAttribute(“ID”);
var vNtID = portalWnd.oUserProfile.getAttribute(“lawsonuserlogin”);
var vMessage=”User Cannot Modify GL Entry”;
var vCompany=lawForm.getDataValue(“GLC-COMPANY”);
vCompany=portalWnd.strFillChar(vCompany,4,”left”,”0″);

var vFYear=lawForm.getDataValue(“GLC-FISCAL-YEAR”);
var vAPeriod=lawForm.getDataValue(“GLC-ACCT-PERIOD”);
var vSystem=lawForm.getDataValue(“GLC-SYSTEM”);
var vJeType=lawForm.getDataValue(“GLC-JE-TYPE”);
var vCountrolGrp=lawForm.getDataValue(“GLC-CONTROL-GROUP”);
var vJeSeq=lawForm.getDataValue(“GLC-JE-SEQUENCE”);

// build the DME call that will get the related asset number
var vDmeString = portalWnd.DMEPath;
vDmeString += “?PROD=DEVRY&FILE=GLCONTROL&FIELD=OPERATOR;&MAX=1&INDEX=GLCSET1”;
vDmeString += “&KEY=” + vCompany + “=” + vFYear + “=” + vAPeriod + “=” + vSystem + “=” + vJeType + “=” + vCountrolGrp + “=” + vJeSeq;
vDmeString += “&SELECT=OPERATOR=” + vNtID;
vDmeString += “&XCOLS=TRUE”;
vDmeString += “&OUT=XML”;

// send the DME call to the server
var vDMEInfo = portalWnd.httpRequest(vDmeString);

if (!vDMEInfo || vDMEInfo.status)
{
var msg=”Error calling DME, “;
msg += (vDMEInfo
? “(status code): “+vDMEInfo.status
: “bad server response.”);
lawForm.setMessage(msg);
alert(msg);
return false;
}

// create an XML object to contain the DME data
var vObjDMEXML = new portalWnd.DataStorage(vDMEInfo);

var vOpr=lawForm.getDataValue(“OPERATOR”);

// load a variable with the records returned by DME
var vRecords = vObjDMEXML.document.getElementsByTagName(“RECORD”);
if (vRecords.length != 1)
{
var vMsg = “Cannot Modify GL Entry”;
lawForm.setMessage(vMsg);
return false;
}

}
return true;
}

]]>
</XSCRIPT>
</form>

 

This shows the program is a Design Studio form formid=”GL40.2_CUSTOM”. The reason it didn’t show properly aligned to the Lawson Portal is because some of the size of the boxes did not match the Portal and DS form.

Resolution:

Run the analyzer tool from Lawson Portal.

Go to Portal > Migrate Custom Content > Migrate Custom Content > Migrate>Custom Form Nodes

You will get Pop ups for the custom form to migrate.

Click ok

And then go to Portal and try your screen again. It should not have the right size.

A unique but not uncommon statistic that came in the wake of the Covid-19 pandemic was the amount of mergers and acquisitions (M&A) that occurred in the last four years. M&As have become a strategic imperative for many companies looking to bolster their market positions and expand their capabilities. Cybersecurity expert Tony Bradley shares an article on Forbes that highlights the increasing significance of cybersecurity in mergers and acquisitions. As companies pursue growth through M&A, they face heightened cybersecurity risks that can impact the success of these deals. The article outlines several key points, including:

  • Rising Threat Landscape: The digital landscape is evolving, with cyberattacks becoming not only more frequent but also more sophisticated. This includes advanced persistent threats (APTs), ransomware, and phishing schemes specifically targeting organizations during the M&A process. The awareness of these risks necessitates a robust evaluation of potential targets’ cybersecurity measures to mitigate risks associated with vulnerabilities that attackers might exploit during or after the acquisition. Companies must be proactive in understanding the threat environment and the specific vulnerabilities that may exist within the target’s infrastructure.
  • Due Diligence: Due diligence in M&A traditionally focused on financial, legal, and operational considerations. However, in today’s environment, cybersecurity has emerged as a critical factor in the due diligence process. Companies are increasingly required to conduct comprehensive cybersecurity audits and assessments to uncover potential issues—such as data breaches or inadequate security practices—that could pose risks post-acquisition. This may involve reviewing the target’s cybersecurity policies, incident response plans, compliance with standards, and historical data breach incidents. Identifying these vulnerabilities early can inform negotiations, affect deal value, and ultimately protect the acquiring company’s interests.
  • Integration Challenges: After the merger, integrating two organizations often presents significant cybersecurity challenges. Differences in cultures, security protocols, network architecture, and technologies can create disparities that may become points of vulnerability. Effective integration means aligning the cybersecurity policies and practices of both entities to create a unified strategy that protects against potential threats. This can include the implementation of consistent security policies across both organizations, joint training programs for employees, and the harmonization of security technologies. Neglecting these factors can lead to gaps in security posture and increased exposure to cyber threats.
  • Regulatory Compliance: As regulations surrounding data protection and privacy become more stringent (e.g., GDPR, CCPA), companies must recognize the legal implications of inadequate cybersecurity during M&A activities. Non-compliance can lead to significant fines and reputational damage in addition to affecting the transaction itself. Companies need to ensure that both they and their potential acquisition targets adhere to pertinent regulations by prioritizing cybersecurity in their M&A strategies. Integrating compliance considerations into the M&A process requires maintaining an ongoing dialogue between legal, financial, and IT teams to ensure that all aspects of regulatory requirements are addressed.
  • Investment in Cybersecurity: As companies acknowledge the critical importance of cybersecurity, there has been a marked increase in investment in security infrastructure and capabilities. This includes implementing advanced security technologies (such as intrusion detection systems, encryption, and identity management), enhancing training programs for employees, and establishing incident response teams. Protecting intellectual property and sensitive customer data is essential during M&A transactions, as these assets significantly contribute to a company’s value. Demonstrating a robust cybersecurity framework can not only safeguard assets but also enhance the acquiring company’s reputation and trustworthiness in the eyes of stakeholders.

Cybersecurity is no longer an afterthought in the M&A process; instead, it should be an integral consideration at every step of the journey—from initial assessments of targets to the final integration of organizations. Emphasizing comprehensive, well-coordinated cybersecurity strategies will safeguard investments and ensure the resilience and success of the combined entities in an increasingly volatile digital landscape.

 

For Full Article, Click Here

As organizations migrate to the cloud, cybersecurity threats have grown, making security a top priority. This shift is driven by the realization that data breaches can have devastating financial and reputational impacts. Businesses are now prioritizing the protection of sensitive data, often opting to invest more in security measures despite potentially higher costs. David S.Linthicum, industry expert and thought leader, shares an article on Infoworld.com on why cloud security typically prioritizes and outranks cost and scalability for some companies. Linthicum explains how the shift in prioritizing cloud security over cost and scalability is a significant trend driven by several factors. Some include: rising cyberthreats, complex cloud environments, compliance and regulatory pressures, reputation, long-term cost implications, innovation and agility. “This landscape is driving businesses to adopt a ‘security-first’ mindset,” he notes.” Although this can be a platitude, we must recognize that other benefits of cloud computing—cost savings and scalability—can be undermined without good security planning and mechanisms. This shift mirrors a broader global movement toward valuing resilience and reliability alongside traditional operational metrics.”

How can companies keep security and cloud costs within a reasonable budget? Balancing cloud costs with security involves strategic approaches to optimize resources while safeguarding systems and data, Linthicum explains. “This directly correlates with the price of the cloud versus the value of security, and they are not often that easy to connect. Many assume that the more security you’ll need, the higher the cost of the cloud services.” However, he has found that in many instances that the opposite is true.

Below are Linthicum’s words of advice to help you find value in security and move away from the accepted mentality that more security always means more money.

  • Build security into the architecture from the start to avoid expensive fixes later. This seems obvious but it’s often not done. Security is an afterthought about half the time, and companies then are forced to toss money at the problem.
  • Automate compliance and management to reduce manual efforts and costs. Automation means repeating good processes without depending on humans; security is no different.
  • Use strong access controls to ensure only authorized users access critical data. Identity management is the most used approach here, and for good reason.
  • Regularly audit cloud usage to eliminate wasteful spending and optimize resource allocation. Also, train teams to efficiently manage cloud resources and security.

 

For Full Article, Click Here

If you’re in Lawson on PO20 and you’re trying to delete a PO, you may sometimes come across the following error message, “Cannot delete, line ###### has been issued”.

 

There is a reason why you cannot delete and a workaround for it. The reason for it not being able to be deleted is that unfortunately, since the PO has been issued, the vendor has a copy of that PO. This means that it is a binding document. It cannot be deleted. It needs to be kept in the system so that it can be referenced if the vendor should call about it. The only action you can take is that the PO can be canceled instead.