https://verint14-pre-02.socialedgeconsulting.io/practice-a/en-US14.0.0.622 14https://verint14-pre-02.socialedgeconsulting.io/practice-a/i/practice-ideas/please-check-out-this-updated-code-we-can-use-for-merging-requestsTue, 07 Feb 2023 20:19:00 GMTidea:f5586d93-f562-4bb4-afa1-b5ec194918a9Please Check Out This Updated Code We Can Use For Merging Requests - please see belowideashttps://verint14-pre-02.socialedgeconsulting.io/practice-a/i/practice-ideas/3rd-party-content-to-magnolia-s-search-integration-without-google-cloudsearchWed, 04 May 2022 13:23:00 GMTidea:b8e7b94f-bb23-4238-bb13-4dbd7671ae80Dear all A customer reached out to us to find a way to integrate ServiceNow content (e.g. IT instructions) to the Magnolia's Search Engine. They do not use Google CloudSearch. Are there any experiences with 3rd party content in the Magnolia's default search engine in general and ServiceNow content in particular? Maybe already working connectors? Any inputs welcome. Thanksideasthird party contenthttps://verint14-pre-02.socialedgeconsulting.io/practice-a/i/practice-ideas/update-in-the-product-notificationsWed, 04 May 2022 13:20:00 GMTidea:11e9efcc-318f-4e1a-9fe0-20060edfaa55Today, you can manage your notifications from the settings and choose to receive them by email. Until now, the email address sending these emails was " noreply@magnolia.com ", but it will no longer be the sender. From now on, all email notifications coming from any Magnolia platform will be sent by an email address attached to the domain “ @updates.magnolia.com ”. Make sure to check your spam folder if you don't receive notifications from Magnolia's' platform anymore, and keep this in mind if customers come to you with this issue. Please note that all Magnolia customers will receive an email with the information on Friday 16th, 2021.ideasproduct notificationshttps://verint14-pre-02.socialedgeconsulting.io/practice-a/i/practice-ideas/a-child-site-to-deal-with-complex-metadataWed, 04 May 2022 13:18:00 GMTidea:b9eb2715-e37e-4ed8-88d1-ca7086eab14dHello everybody, a project for a client has quite a complex structure. They will have a common area and then different unit pages. We're having some doubts when dealing with the metadata of a specific unit that will be used to search and filter content. Since those metadata are valuable for only one part of the group we were thinking of creating a Child Site dedicated to the specific area so that the metadata structure won’t be mixing with the other elements. Has any of you already had to deal with a similar situation? Any suggestions on how to deal with that? THis has been reviewed and planned for a future releaseideasmetadatahttps://verint14-pre-02.socialedgeconsulting.io/practice-a/i/practice-ideasTue, 26 Apr 2022 16:37:00 GMTideation:da452de0-62f7-40e8-a85c-01e45e90f497