Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Event colors (LP 46799470) #73

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

easafe
Copy link
Member

@easafe easafe commented Apr 22, 2023

Custom field to set event background.

Custom field to set event background.
@cwarden
Copy link
Member

cwarden commented Apr 22, 2023

Let's use the value of the picklist options to store the color values, e.g. #cccccc, and the picklist option labels to store the descriptive names like Violet. This will allow customers to define their own colors if desired.

@@ -16,14 +16,17 @@ export type Event = {
ShowAs?: string,
StartDateTime: Date | number,
Subject: string,
WhatId?: Id
WhatId?: Id,
Color__c?: string
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The field will be namedspaced in the managed package, so it'll be oscal__Color__c.

The field also needs to be added to the remoteObjectModel in the Calendar Visualforce page so it's actually retrieved.

And the field needs to be added as an available field to the CreateEvent field set so customers can include it in the set of fields displayed when editing an event in Lunasa.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does the field also need to be namespaced on the remote object and create event?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Visualforce page will handle the namespace automatically.

The javascript side needs to figure out the namespace. We could add a property to the Visualforce page that contains the namespace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants