Sage CRM 2023 R1 - 发行说明报告

SageCRM2023R1

ReleaseNotes

Updated: April2023

SageCRM2023R1-ReleaseNotes

Page

PAGE

4

of

NUMPAGES

32

©2023,TheSageGroupplcoritslicensors.Allrightsreserved.Sage,Sagelogos,andSageproductandservicenamesmentionedhereinarethetrademarksofTheSageGroupplcoritslicensors.Allothertrademarksarethepropertyoftheirrespectiveowners.

Contents

Overview

5

Releasedateandfilesincluded

6

Documentationandhelp

7

Installingandupgrading

8

Installationprerequisites

8

Upgradepath

8

Post-installation/upgradetasks

9

Supportedthemes

10

Newfeaturesandenhancements

11

Editfileswithoutinstallingplugin

12

EditfileattachedtoCompanyorTask

12

EditfilecreatedwithMailMerge

13

Enhancedemailimport

14

ImportemailsintoCasesandcustomentities

14

UIimprovements

15

Enablepre-2023R1customentityforemailimport

16

ViewnarrativesummaryforCompany

17

CustomizeSageCRMloginscreen

19

ExampleChangeLogonLogo.jsfile

20

Examplecustom-logon.cssfile

21

Allowfilenameextensionsforupload

22

Refreshedbrand,enhancedaccessibility

23

Improved.NETdocumentation

23

Supportfornewsoftware

23

Addressedissues

24

Discontinuedfeatures

29

Knownissuesandlimitations

30

Overview

Thisdocumentprovidesinformationaboutthenewfeaturesandenhancementsimplemented,issuesaddressed,andissuesknowntoexist(ifany)intheSageCRM2023R1release.ItisintendedforSageOpCos,SageCRMpartners,andSageCRMcustomers.

WhilethisdocumentreferstoSageCRM,regionalproductsmayusedifferentbrandnames.

Dependingontheregionyouarein,youcanobtainlicensekeysforSageCRM2023R1toinstallspecificproductmodulessuchasSales,Marketing,andService(orcombinationsofthesemodules).Formoreinformationontheavailabilityofmodulesandtheconfigurationsavailableinyourregion,pleasecontactyourlocalSageoffice.

WheninstallingSageCRM2023R1,youcanoptionallyselecttosendanonymousSageCRMusagestatisticstoSagethroughGoogleAnalytics.ThisinformationwillallowSagetoimprovetheservicesandsoftwareweprovidetoourcustomers.

Releasedateandfilesincluded

Releasedate eWare.dllversion

March2023

Documentationandhelp

Toviewcontext-sensitivehelp,clicktheHelpbuttoninSageCRM2023R1.

FormoreinformationaboutthesoftwarewithwhichSageCRM2023R1canworkandintegrate,seethe2023R1HardwareandSoftwareRequirementspostedonthe

SageCRMHelpCenter

.

ForonlineUserHelp,onlineSystemAdministratorHelp,andallPDFdocumentationforthisrelease,gotothe

SageCRMHelpCenter

.

Note:Translatedhelpandguideshavebeendiscontinued.OnlyEnglishdocumentationisnowsuppliedwithSageCRM.

Installingandupgrading

Note:InstallonlyoneSageCRMinstanceperserver.Sagedoesn'tsupportconfigurationswheretwoormoreSageCRMinstancesareinstalledonthesameserver.

Installationprerequisites

BeforeinstallingorupgradingSageCRM,makesurethat:

YourenvironmentmeetstheSageCRM2023R1HardwareandSoftwareRequirementspublishedonthe

SageCRMHelpCenter

.

YouhaveMicrosoftOLEDBDriverforSQLServerinstalledontheSQLServerthatwillbehostingtheSageCRMdatabase.

DownloadMicrosoftOLEDBDriverforSQLServer

Youneedtoinstalldriverversion18orlater.Ifyoudon'thavethisdriverinstalled,theSageCRMSetupcannotconnecttotheSQLServer.

Upgradepath

YoucanusetheSageCRM2023R1installationpackagetoupgradefromversions2022R2,2022R1,2021R2,2021R1,2020R2,and2020R1.

ToupgradefromanearlierversionofSageCRM,pleasefirstupgradetooneoftheversionslistedhere.

Note:Computertelephonyintegration(CTI)hasbeenremovedfromSageCRM2023R1andisnolongersupported.IfyouhaveCTIinstalledinapreviousSageCRMversion,upgradingto2023R1completelyremovesCTI.

Post-installation/upgradetasks

SageCRMSetupcannotupgradeMicrosoftSQLServerExpressinstalledwithapreviousSageCRMversion.Asaresult,youmayendupwithSageCRMusinganunsupportedMicrosoft

SQLServerExpressversion.Ifnecessary,manuallyupgradeMicrosoftSQLServerExpressafterupgradingSageCRM.

ForsupportedMicrosoftSQLServerExpressversions,seeSageCRM2023R1HardwareandSoftwareRequirementspublishedonthe

SageCRMHelpCenter

.

MakesurethatuserpasswordsinSageCRMarenotblank.WetestSageCRMfeaturesinanenvironmentwhereeveryuserhasanonblankpasswordassigned.Ifyouhaveblankuserpasswordsinyourenvironment,SageCRMfeaturesmaybehaveunpredictably.

LogontoSageCRMasasystemadministratoratleastoncebeforeupgradingtothenextversion.ThisisrequiredtoupdatetheSageCRMdatabasecorrectly.

CleartheWebbrowsercacheoneachuser'scomputertoensuretheInteractiveDashboardworkscorrectly

Re-entertheSageCRMsystemadministratorpasswordafteryouhaveupgradedSageCRMthatisintegratedwithanothersystem.Thisisrequiredtohashandsecurelystorethepassword.

LogontoSageCRMasasystemadministrator.

Goto|Administration|Integration|IntegrationListandclicktheintegrationforwhichyouwanttore-enterthepassword.

SelectDisableandthenselectContinue.

SelectChange.

IntheCRMPasswordtextbox,re-enterthepassword.

SelectSave.

SelectEnable.

Note:Youmustre-entertheSageCRMsystemadministratorpasswordusingthestepsabovewheneveryoumodifyyourintegration.

SageCRM2023R1-ReleaseNotes

Page

PAGE

20

of

NUMPAGES

32

Supportedthemes

TheonlysupportedSageCRMthemeisContemporary.

WerecommendthatafterinstallingorupgradingSageCRMsystemadministratorsmakesurethattheContemporarythemeissetasthedefaulttheme.

Fordetails,seeChangingthedefaultthemeintheSageCRM2023R1SystemAdministratorHelp

publishedonthe

SageCRMHelpCenter

.

Newfeaturesandenhancements

SageCRM2023R1providesthefollowingnewfeaturesandenhancements:

Editfileswithoutinstallingplugin

Enhancedemailimport

ViewnarrativesummaryforCompany

CustomizeSageCRMloginscreen

Allowfilenameextensionsforupload

Refreshedbrand,enhancedaccessibility

Improved.NETdocumentation

Supportfornewsoftware

Editfileswithoutinstallingplugin

FeatureID:CRMS-23,CRMS-385,CRMS-1059,CRMS-1162

UsersnolongerneedtoinstallaplugintoviewandeditafileattachedtoaCompanyorTask,orcreatedusingtheMailMergefeature.Nowausercandownloadthefilelocally,openandedititintherelevantapplicationinstalledontheircomputer,andthenuploadthefilebacktoSageCRM.

ThisenhancementallowsuserstoeditfilesinanywebbrowsersupportedbySageCRM.ItalsosupportstheretirementofMicrosoftInternetExplorer11.

Note:CurrentlySageCRMdoesn'tsupporttheeditingofshareddocuments.

EditfileattachedtoCompanyorTask

SearchforandopentheCompanyorTaskthathasthefileattached.

Downloadtheattachedfileyouwanttoviewandedit:

ForaCompany,selecttheDocumentstab,selectthefilename,andselectView/EditFile.

ForaTask,selecttheAttachmentstab,selectthefilename,andselectView/EditFile.

Openthedownloadedfileintherelevantapplicationinstalledonyourcomputer.Editthefileandsaveyourchanges.

Tip:Youcanspecifythedefaultdownloadfolderin

Loginandsessionpreferences

,sothatSageCRMpromptsyoutoopenthedownloadedfileintherelevantapplicationinstalledonyourcomputer.

Ifyoueditedthefileinstep3,returntoSageCRM,browsetoselectthefile,andthenselect

UploadFile.

Warning:ThenameoftheeditedfileyouareuploadingmustmatchthefilenamedisplayedintheSageCRMuserinterface.Windowsmayhaverenamedthefileduringthedownloadifthetargetfolderalreadycontainedafilewiththesamename.Ifso,renamethefilebeforeuploadingit.

EditfilecreatedwithMailMerge

Searchfortherecordyouwanttouseinthemergeoperation.

Inthesearchresults,selecttherecordsyouwanttouse:

Touseasinglerecord,selecttherecord,selecttheDocumentstab,andthenselect

MergetoWordorMergetoPDF.

Touseallrecordsinthesearchresults,selectMergetoWordorMergetoPDF.

Selectthemailmergetemplateyouwanttouse.

Ifyouwanttoseehowyourmergeddocumentisgoingtolook,selectPreviewMerge.Ifyou'remergingmultiplerecords,thepreviewshowsonlythefirstrecordinthegroup.

SelectMergeandContinueandwaituntilyourmergecompletes.

YoucanselectCreateCommunicationtocreateanewcommunicationandattachthemergeddocumenttoit.Youcanalsoviewandeditthemergedfile.Otherwise,selectContinue.

Toviewandeditthemergedfile:

SelectView/EditFiletodownloadthefileandopenitinanapplicationinstalledonyourcomputer.Editthefileifnecessary.

Tip:Youcanspecifythedefaultdownloadfolderin

Loginandsession

preferences

,sothatSageCRMpromptsyoutoopenthedownloadedfileintherelevantapplicationinstalledonyourcomputer.

Ifyoueditedthefile,returntoSageCRM,browsetoselectthefile,andthenselect

UploadFileandContinue.

Warning:ThenameoftheeditedfileyouareuploadingmustmatchthefilenamedisplayedintheSageCRMuserinterface.Windowsmayhaverenamedthefileduringthedownloadifthetargetfolderalreadycontainedafilewiththesamename.Ifso,renamethefilebeforeuploadingit.

IfyouearlierselectedCreateCommunication,completethe

Detailspanel

fieldsandselectSave.

Enhancedemailimport

NowuserscanimportemailsintoCasesandcustomentities,filteralistofemailstobeimported,viewintowhichrecordanemailhasbeenimported,andusethenewstepsinthedocumentationtoenableapre-2023R1customentityforemailimport.

Forinstructionsonhowtoenableandusetheimportofemails,see

Importingcontactsand

emailmessagesfromExchangeOnline

intheSystemAdministratorHelp.

ImportemailsintoCasesandcustomentities

InthepreviousSageCRMrelease,theimportofemailmessageswasavailableonlyonCompanies,Persons,andOpportunities.Inthisrelease,userscanalsoimportemailsintoCasesandcustomentities.TheimportofemailsintoCasesisworkingoutofthebox.Toenabletheimportofemailsforacustomentity,asystemadministratorneedstoactivateread-onlySDataexternalaccessforthatentity:

Goto|Administration|Customization|<customentityname>.

OntheExternalAccesstab,selectChangeandsetRead-onlySDatatoYes.

SelectSave.

Ifthecustomentitywascreatedwithapre-2023R1versionofSageCRM,completetheadditionalstepsinthenextsection.

Enablewriteaccesstothecomm_caseidfieldofCommunication.ThisisrequiredsothatusersandinfomanagerscouldviewtheCaseintowhichanemailisimported.

Goto|Administration|Customization|Communication.

IntheFieldNamecolumn,locatecomm_caseid.

Intherowwherecomm_caseidislocated,selecttheeditbutton()intheFieldSecuritycolumn.

IntheWriteAccesscolumn,selectAllow,andselectContinue.

Nowuserscanstartimportingemailsintothecustomentity.

UIimprovements

WhenauserselectstheImportEmailsbuttonandviewsalistofemailstobeimported,theycan:

Filteremails.Bydefault,thelistdisplaysallemailmessagesresidingintheExchangeOnlinefolderselectedbytheuser.ThisincludesthemessagesthathavebeenimportedintoSageCRMearlier.NowuserscanselectHideimportedemailstohidethemessagesthathavealreadybeenimportedintoSageCRM.

Viewtherecordintowhichanemailhasbeenimported.ThisinformationisavailableintheFiledAgainstcolumnaddedinthisrelease.TheFiledAgainstcolumnusesthefollowingformatstoshowtherecordagainstwhichaparticularemailhasbeenfiled.ThecolumnshowstheparentPersonandCompanyonlyiftherecordhasthem.

Entity FormatusedinFiledAgainstcolumn

Case Casereference(parentPersonname;parentCompanyname)Company Companyname

Customentity Customentityname(parentPersonname;parentCompanyname)*

Note:Theasteriskindicatesthatthisisacustomentityrecord.

Opportunity Opportunitydescription(parentPersonname;parentCompanyname)Person Personname(parentCompanyname)

Enablepre-2023R1customentityforemailimport

Toenabletheimportofemailsforacustomentitycreatedwithapre-2023R1versionofSageCRM,asystemadministratorneedstocompletethebelowadditionalsteps.ThesestepsarenotneededforcustomentitiescreatedwithSageCRM2023R1andlater.

OnaSageCRMserver,goto<SageCRMinstallationfolder>\WWWRoot\CustomPages\<entityname>.

ThedefaultSageCRMinstallationfolderis

%ProgramFiles(x86)%\Sage\CRM\CRM

Openthe<EntityName>Summary.aspfileinacodeeditor.

Locatethefollowinglineofcode:

CRM.AddContent(Container.Execute(record));

Immediatelyabovethisline,insertthefollowingcode:

recObj=CRM.FindRecord("Custom_Tables","Bord_Name='"+Entry.Title+"'");if((true)&&(recObj('Bord_HasCommunication')!=undefined)){

recObjOAuth=CRM.FindRecord("UserSettings","USet_Key='EMC_AuthAccessToken'andUSet_UserId='"+CRM.GetContextInfo('User','User_UserId')+"'");

if((true)&&(recObjOAuth.RecordCount>0)){Container.AddButton(CRM.Button("ImportEmails","",CRM.URL(1362)+

"&ImportMode=0&EntName="+Entry.Title+"&EntIdField="+recObj('Bord_IdField')));

}

}

Saveyourchanges.

ViewnarrativesummaryforCompany

SageCRM2023R1usesadeterministicartificialintelligenceapproachtogenerateanddisplayanarrativereportcontaininganexecutivesummaryandbusinessinsightsforeachCompany.

Thisnewfeatureautomaticallyanalyzesthesales,customerservice,andcommunicationdataandpresentsitasashortandeasy-to-understandnarrativereportonaNarrativetabdisplayedforeachCompany.InthisSageCRMrelease,theNarrativetabprovidesinformationinEnglishonly.

Thenarrativereportismorememorable,persuasive,andengagingthandataalone.Itsummarizeseverythingthereaderneedstoknowaboutthecompanywithouthavingtolookattherelatedrecordsandconverttherawdataintoinformation.

ThenarrativereporttakesintoaccountthesecuritypoliciesexistinginSageCRM,sothatthegeneratedinformationistailoredtotheuserwhoisaccessingtheNarrativetab.Thispreventsunauthorizedaccesstosensitivedataandmakesthedisplayedinformationmorerelevantandusefulforspecificaudiences.

Asasystemadministrator,youcancontrolwhatinformationisavailabletoauserontheNarrativetab.Toshoworhideinformation,edittheuser'ssecurityprofiletograntorrevoketheViewrightinthecorrespondingoption,asshowninthetable.

AreaonNarrativetab ControlledbyViewrightinthissecurityprofileoption

CompanyAddressRelationships

Company

Warning:RevokingtheViewrightinthissecurityprofileoptionmakesCompaniesinaccessibletotheuser.

Communication Communication

Sales Opportunity

Cases Cases

Forexample,tohideinformationintheSalesareaoftheNarrativetab,makesurethattheuserdoesnothaveViewrightsonOpportinitiesintheirsecurityprofile.

Youcanconfiguresecurityprofilesin|Administration|Users|Security|SecurityProfiles.

CustomizeSageCRMloginscreen

FeatureID:CRMS-1301

Withthisnewfeature,youcan:

Displayandpositionyourcustomlogoontheloginscreen.

Changethebackgroundoftheentireloginscreen,itstoparea(wheretheSagelogoislocated),itsmiddlearea(wheretheloginformislocated),oritsbottomarea.

Toperformthesecustomizations,youcanusethepreconfigured.cssand.jsfilessuppliedwithSageCRM.

OnaSageCRMserver,locatethefollowingfiles:

Filename Location

custom-logon.css

Usethisfiletochangethebackgroundcoloroftheloginscreenandtopositionyourcustomlogo.

<SageCRMinstallationfolder>\WWWRoot\Img\logon\css

Note:Bydefault,SageCRMisinstalledto

%ProgramFiles(x86)%\Sage\CRM\CRM.

ChangeLogonLogo.js

Usethisfiletospecifythenameofthefilethatstoresthecustomlogoyouwanttodisplayontheloginscreen.

Youcanstoreyourcustomlogoina

.gif,.jpeg,.png,or.svgfile.Thefilenamecanincludethefollowingcharactersonly:

A-Z,a-z,0-9,underscore(_),fullstop(.),andhyphen(-).

<SageCRMinstallationfolder>\WWWRoot\Img\logon\js

Editthecustom-logon.cssandChangeLogonLogo.jsfilestosetthedesiredbackgroundcolorandspecifythenameofyourcustomlogofile,ifnecessary.Fordetails,seetheannotationsinthefiles.

Saveyourchanges.

Ifyouwanttodisplayacustomlogo,copyyourcustomlogofileto

<SageCRMinstallationfolder>\WWWRoot\Img\logon\gif.

Copytheeditedcustom-logon.cssandChangeLogonLogo.jsfilestothefollowinglocations.SkipcopyingChangeLogonLogo.jsifyoudon'tneedtodisplayacustomlogo.

Filename Copyto

custom-logon.css <SageCRMinstallationfolder>\WWWRoot\Themes\custom

ChangeLogonLogo.js <SageCRMinstallationfolder>\WWWRoot\js\custom

NowyoucanopentheSageCRMloginscreentoviewyourcustomizations.

Note:WhenyouupgradeSageCRM,theSageCRMSetupdoesnotreplaceormodifythe

custom-logon.cssandChangeLogonLogo.jsfilesinthelocationsyoucopiedthemto.

ExampleChangeLogonLogo.jsfile

ThisisthecontentsoftheChangeLogonLogo.jsfilesuppliedwithSageCRM.

1 /*

2 ©2023,TheSageGroupplcoritslicensors.Allrightsreserved.

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

Usethisfiletospecifythenameofthefilethatstoresthecustomlogoyouwanttodisplay

ontheloginscreen.

Toactivatethisfile,copyitto:

<SageCRMinstallationfolder>\WWWRoot\js

Youcanstoreyourcustomlogoina.gif,.jpeg,.png,or.svgfile.

Thefilenamecanincludethefollowingcharactersonly:

A-Z,a-z,0-9,underscore(_),fullstop(.),andhyphen(-).

ReplaceMyLogo.pngonline20withtheactualnameofyourcustomlogofile.Copyyourcustomlogofileto:

<SageCRMinstallationfolder>\WWWRoot\Img\logon\gif

*/

$(function(){

letlogo="LeftLogo";

$('#'+logo).children('img').attr("src",function(index,attr){

returnattr.replace(logo+".png","MyLogo.png");

})

});

Examplecustom-logon.cssfile

Thisisthecontentsofthecustom-logon.cssfilesuppliedwithSageCRM.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

/*

©2023,TheSageGroupplcoritslicensors.Allrightsreserved.

UsethisfiletocustomizetheappearanceoftheSageCRMloginscreen.

Toactivatethisfile,copyitto:

<SageCRMinstallationfolder>\WWWRoot\Themes\custom

Ontheloginscreen,theHTMLelementscontrolledbythisCSSarenestedasfollows:

<body>

<divid="LogonPageBody">

<divid="LogonForm">

<divid="HeaderImage">

</div>

</div>

</div>

</body>

Asaresult,HeaderImageoverridesLogonForm,andLogonFormoverridesLogonPageBody.

*/

/*Positionsyourcustomlogoimageontheloginscreen.*/#LeftLogo{

position:relative;top:300px;

left:100px;

}

/*Setsthebackgroundcoloroftheentireloginscreen.*/#LogonPageBody{

background-color:green;

}

36

37

38

39

40

/*Setsthebackgroundcoloroftheloginscreenareawheretheloginformislocated(the

middleofthescreen).*/#LogonForm{

background-color:white;

}

41

42

43

/*SetsthebackgroundcoloroftheloginscreenareawheretheSagelogoislocated(thetop

ofthescreen).*/#HeaderImages{

background-color:orange;

}

Allowfilenameextensionsforupload

SystemadministratorscanconfigureanallowlisttorestrictthefiletypesthatuserscanuploadtoSageCRM.Ifafilenameextensionismissingfromtheallowlist,theuploadofthefileisblocked.

Theserestrictionsapplywhenauser:

UsestheAddFilebuttonorDropfilesheretoattachthemareatouploadfilesonthe

SharedDocumentstaborattachfilestoacalendartask,emailmessage,orcommunication.

SelectstheImportEmailsbuttontofileemailsagainstarecordinSageCRM.

ThisnewfeaturereplacestheblocklistFileextensionrestrictions,whichhasbeen

discontinued

.

Warning:Duringupgrading,theSageCRMSetupdoesnottransferthefilenameextensionsfromtheblocklistFileextensionrestrictionstoSageCRM2023R1.Youneedtotransfertheserestrictionsmanually.

Toallowfilenameextensionsforupload:

Goto|Administration|EmailandDocuments|Documents&ReportsConfiguration.

Configurethefollowingoptions:

Allowedfilenameextensionsforupload.PopulatethisoptionwiththefilenameextensionsthatcanbeuploadedtoSageCRM.Omitfullstopfromthefilenameextensions.Useacommaasaseparator.

Thedefaultvalueinthisoptionis:

doc,docx,rtf,xls,xlsx,ppt,pptx,pdf,csv,xml,txt,jpg,jpeg,bmp,gif,png,svg,zip

Ifafilenameextensioninthisoptionbelongstoanexecutablefile,youmustalsosetAllowexecutablefilestobeuploadedtoYes.SageCRMtreatsthefollowingfiletypesasexecutable:

com,cpl,dex,dll,exe,fon,mz,scr,sys,iec,ime,rs,tsp

Allowexecutablefilestobeuploaded.Toallowtheuploadofexecutablefiles,setthisoptiontoYesandaddthefilenameextensionsofexecutablefilestoAllowfilenameextensionsforupload.

Todetectanexecutablefile,SageCRMchecksthefile'sheadertodetermineitstruetype.ThismakesSageCRMcapableofdetectinganexecutablefileevenifitsfilenameextensionhasbeenchanged.

Refreshedbrand,enhancedaccessibility

WehaverefreshedtheSageCRMuserinterfacetomakeitconsistentwiththenewvisualidentityoftheSagebrand,enhanceourcustomers'experiences,andimprovetheUIaccessibility.

TheUInowfeatures:

Anewfont

Anewsetofrecognizableandconsistenticons

AnewcolorschemeimprovingtheoverallaccessibilityoftheUI

Improved.NETdocumentation

Wehavemovedthe.NETAPIandSDKdocumentationfromthe

DeveloperHelp

tothe

Developer

Portal

.Wehavealsoaddedanup-to-datesearchable

.NETAPIreference

.

Supportfornewsoftware

MicrosoftSQLServer2022.YoucanconfigureSageCRMtostoredatainadatabasehostedonMicrosoftSQLServer2022Standard,Enterprise,Web,orExpress.

MicrosoftSQLServer2022ExpressisbundledwiththeSageCRM2023R1installationpackage,andyoucaninstallthisSQLServereditionwheninstallingSageCRM.

BeawarethatMicrosoftSQLServer2022Expresshasanumberoflimitations.Fordetails,seetheSageCRM2023R1HardwareandSoftwareRequirementspublishedonthe

SageCRMHelp

Center

.

Addressedissues

Thefollowingisalistofcustomercasesaddressedinthisrelease.

IssueID Area Description Status

CRMS-1050 Calendar

Calendarlist

CRMS-923 CalendarCalendarlist

WhentheTaskstabofthecalendarwasconfiguredtoshowoverduetaskswhosestatuswasInProgress,notaskswereshowneventhoughtheyactuallyexisted.

AuserwhohadsufficientrightsontheCommunicationentitycouldnotdraganddropanappointmentinthecalendar.

Thisissueoccurredinthefollowingscenario:

Asystemadministratorcreatedanewcustomprofilewiththefollowingsettings:

User'shometerritory:Communication:View/Ins

Assignedto:Communication:View/Edit/Del

Thesystemadministratorassignedthecustomprofiletoauser.

TheusercreatedanappointmentontheWorkWeektabofthecalendarandtriedtodraganddroptheappointmenttoanewdate.

Thisissueisfixed.

Thisissueisfixed.

SageCRM2023R1-ReleaseNotes

Page

PAGE

26

of

NUMPAGES

32

IssueID

Area

Description

Status

Asaresult,anemptySageCRMwindowwithanOKbuttonappearedandthefollowingerrorwasobservedontheNetworktabintheDeveloperTools(F12)ofthewebbrowser:

"Youdonothavetherequiredsecuritypermission<username>-Communication."

CRMS-1264,CRMS-1310

Coreproduct

SageCRMdidnotreleasethedatabaseconnectionsitcreated.

Thisissueisfixed.

Asaresult,SageCRMexceededthemaximumnumberofconnectionsandthefollowingerrorwaswrittentotheSageCRMlogfile:

“CouldnotopenaconnectiontoSQLServer.”

CRMS-1152,CRMS-1157

Customization

WhenauserattemptedtoopenacustomentityrecordfromtheRecentlist,anerroroccurred.

Thisissueisfixed.

Thisissueaffectedthecustomentitiesthathad:

CompaniesandPersons.

and

ThefollowinglineofcodeintheProjectSummary.aspfile:

varuserid=

CRM.GetContextInfo("User",

"user_userid");

CRMS-1131

CustomizationQuickFindSearch

ThefollowingissuesoccurredwhentheregioninWindowswassettoHongKongSARandthelanguagewassettoChinese(Traditional,HongKongSAR):

Thisissueisfixed.

SearchSelectAdvancedfieldsthathadrestrictedvaluesfailedtowork,returning"Fieldvalueis

IssueID Area Description Status

notcorrect".

SearchandQuickFinddidn'twork.

CRMS-1222 Email WhenasystemadministratorenabledOAuth2.0inEmailManagementServerOptions,thefollowingerrorwaswrittentotheSageCRMlogfile:

"ExceptionconnectingtoMailServer:SSLIOHandlerisrequiredforthissetting."

ThisissuewascausedbytheincorrectdescriptionoftheSMTPserverfieldintheSystemAdministratorHelp,whichwronglystated"Ifleftblank,EmailManagementusesyourPOPserverforoutboundmails."

Documentationupdatedtoprovidethecorrectdescriptionofthe

SMTPserver

field.

CRMS-1049 Exchange

Integration

CRMS-1109 Importcontactsandemails

CRMS-1154 Importcontactsandemails

ThesynchronizationofappointmentsbetweenSageCRMandExchangeOnline(Office365)permanentlyfailed.

WhenauserimportedanemailintoaCompany,theemail'sterritorywaserroneouslysettoNone.

TheexpectedbehaviorinthiscaseisthattheCompany'sterritoryshouldbeappliedtotheemail.

WhenauserselectedanemailtoimportandthenselectedImportemails,thefollowingerrordisplayed:

"Theresourcecannotbeprocessed."

Thisissueoccurredonlyifthecomm_channelidfieldwasnotsetto4.

Thisissueisfixed.

Thisissueisfixed.

Thisissueisfixed.

CRMS-911,CRMS-460

Leads WhenausercreatedanewWebLead,thevaluesofthelead_statusandlead_stagefieldswerepopulatedwiththewrongvalues.

Thisissueisfixed.

IssueID

Area

Description

Status

Thisissueoccurredafterasystemadministrato