When using this API many times in a row to try and populate real policy
descriptions/resolutions, I discovered a problem: the inferred
resolution (“What we’ll do”) almost never used decisive language, so
you'd get a lot of “probably”, etc., when we really want it to sound
more confident about what will happen during the maintenance window.
(The calendar events say what WILL happen to your device, not what
should probably happen.)
After several attempts to tweak the prompt, I ended up getting the best
results by just removing "probably" from
`whatWillProbablyHappenDuringMaintenance`. I made this change to the
prompt without changing the data that this API returns.
---------
Co-authored-by: Eric <eashaw@sailsjs.com>
Closes: https://github.com/fleetdm/confidential/issues/6268
Changes:
- Updated the questionnaire on the /start page to take users who answer
"I'd like you to host Fleet for me" on the "What did you think?" step to
the host count question.
- Updated the /start page script to handle this new behavior.
- Updated how psychologicalStage is set for users who answer the host
count question in `save-questionnaire-progress`.
- Updated `save-questionnaire-progress` to only call the salesforce
helper if the user's `psychologicalStage` changes.
Changes:
- Added two steps to the /start questionnaire for users who select "I
want to deploy Fleet in my environment" on the "What did you think"
question.
- Updated save-questionnaire-progress to set psychologicalStage based on
selected answers to the new questions
Closes: https://github.com/fleetdm/confidential/issues/6355
Changes:
- Replaced the reqeust to zapier in `signup.js` with
`sails.helpers.salesforce.createLead()`.
- Updated signup.js to only call the salesforce helpers when the website
is running in a production environment.
- Updated the `createLead` to handle errors when retrieving or creating
salesforce records, and to set a provided `numberOfHosts` and
`primaryBuyingSituation` on created lead records.
Proposes a solution to avoid messing with the PR open time KPI when
creating API design draft PRs. (These PRs are created fairly often as
part of the normal product design process, and usually sit in draft for
weeks before they're ready to merge.) See conversation
[here](https://github.com/fleetdm/fleet/pull/16129#issuecomment-2080181953)
for context.
Changes:
- Updated the blurb for the endpoint ops page on the homepage.
- Updated the "automate anything" section on the endpoint ops page to be
the first feature shown on the endpoint ops page (For users with eo-it
or mdm `primaryBuyingSituation`)
Changes:
- Changed the warnings in the get-enriched helper to use
`sails.log.info`.
- Updated the email domain parsing to handle protocol-less URLs returned
from Coresignal
Closes: #18643
Changes:
- Updated the response from the `updateOrCreateAccountAndContact` helper
when running the website in a development environment.
- Updated the Zapier webhook request in the signup action to send the
contact and account IDs returned from the
`updateOrCreateAccountAndContact` helper.
Changes:
- Added a prefix to the warning logged in the send-data-to-vanta script
if an error is thrown.
- Updated the logged errors to include the raw error
Closes: https://github.com/fleetdm/confidential/issues/6289Closes: #16441
Changes:
- Updated the positon and layout of the calendar banner on the homepage
and landing pages.
- Updated the homepage hero image
---------
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
Article: Fleet in your calendar: introducing maintenance windows #18609
---------
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
Related to https://github.com/fleetdm/confidential/issues/6357
Changes:
- Updated `save-questionnaire-progress` to only call
`sails.helpers.salesforce.updateOrCreateContactAndAccount` is called
when a user's `psychologicalStage` changes.
