@aglyn/aglyn 1.0.0-beta.293 → 1.0.0-beta.296
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +11 -11
- package/src/lib/app-utils/crm-kinds.d.ts +7 -1
- package/src/lib/app-utils/crm-kinds.js +11 -0
- package/src/lib/app-utils/crm-kinds.js.map +1 -1
- package/src/lib/app-utils/crm.d.ts +5 -1
- package/src/lib/app-utils/crm.js +51 -4
- package/src/lib/app-utils/crm.js.map +1 -1
- package/src/lib/app-utils/docs-help-sections.generated.js +4 -3
- package/src/lib/app-utils/docs-help-sections.generated.js.map +1 -1
- package/src/lib/app-utils/docs-help.generated.d.ts +1 -1
- package/src/lib/app-utils/docs-help.generated.js +2 -0
- package/src/lib/app-utils/docs-help.generated.js.map +1 -1
- package/src/lib/app-utils/docs-index.generated.js +23 -16
- package/src/lib/app-utils/docs-index.generated.js.map +1 -1
- package/src/lib/app-utils/screen-version-publish.d.ts +71 -0
- package/src/lib/app-utils/screen-version-publish.js +82 -0
- package/src/lib/app-utils/screen-version-publish.js.map +1 -0
- package/src/lib/app-utils/server.d.ts +1 -0
- package/src/lib/app-utils/server.js +1 -0
- package/src/lib/app-utils/server.js.map +1 -1
- package/src/lib/app-utils/version-draft.d.ts +31 -0
- package/src/lib/app-utils/version-draft.js +29 -0
- package/src/lib/app-utils/version-draft.js.map +1 -0
- package/src/lib/plugin-manager/plugin-record-timeline.d.ts +5 -2
- package/src/lib/plugin-manager/plugin-record-timeline.js.map +1 -1
|
@@ -275,21 +275,21 @@ export const DOCS_SECTION_INDEX = [
|
|
|
275
275
|
title: 'AI jobs and activity',
|
|
276
276
|
heading: 'One job\'s page',
|
|
277
277
|
anchor: '#one-jobs-page',
|
|
278
|
-
text: 'A job\'s page shows each step as it happens, with its own state (Done, Waiting, In progress, Paused, Not built or Couldn\'t be built) and the credits each step used. From there you can:\n- Confirm plan, when a plan is waiting for you;\n- Resume a job that paused for credits, or Get more AI credits;\n- Try again, or Try again what failed to build only the parts that failed;\n- Cancel a job that is still running (see Cancel a job);\n- open what it built: View your site, Edit your pages, or the draft itself.\nFor a new site this is the Building your site page; see Start a new site with AI.'
|
|
278
|
+
text: 'A job\'s page shows each step as it happens, with its own state (Done, Waiting, In progress, Paused, Not built or Couldn\'t be built) and the credits each step used. From there you can:\n- Confirm plan, when a plan is waiting for you;\n- Resume a job that paused for credits, or Get more AI credits;\n- Try again, or Try again what failed to build only the parts that failed;\n- Cancel a job that is still running (see Cancel a job);\n- open what it built: for a job that changed one page, Open in Besigner, where Open draft shows a change saved into the page\'s draft, and Preview too when the change was saved as a new version (in a new tab, where you can publish it); otherwise View your site, Edit your pages, or the draft itself.\nFor a new site this is the Building your site page; see Start a new site with AI.'
|
|
279
279
|
},
|
|
280
280
|
{
|
|
281
281
|
path: '/ai/ai-jobs-and-activity',
|
|
282
282
|
title: 'AI jobs and activity',
|
|
283
283
|
heading: 'AI jobs in Assist',
|
|
284
284
|
anchor: '#ai-jobs-in-assist',
|
|
285
|
-
text: 'The AI jobs
|
|
285
|
+
text: 'The AI jobs row at the top of the Assist panel follows your jobs wherever you are in the console, and counts the jobs that need you and are running.\n- On a site, it counts that site\'s jobs, and View all opens the site\'s AI jobs page, where each job has room to be read. Open in AI jobs on a card in the chat opens that job\'s own page there.\n- On a workspace page, such as Billing, the row opens into a list of the workspace\'s jobs. It opens on its own while a job is running or waiting for you, and shows each job\'s steps, credits and plan, with Cancel while it runs.\nThe AI chip in the top bar, beside the notifications bell, appears while any job is running or waiting: AI · plan ready, AI · needs attention, AI · planning or AI · working. Choose it to open that job: on the site\'s AI jobs page when you are on a site, in the list in Assist otherwise.\nA notification arrives when a plan is ready, when a job finishes and when it stops. A plan still waiting for you a day after it was ready gets one reminder, and never another. Turn them off under AI job needs you, AI job finished and AI job stopped in your notification settings.'
|
|
286
286
|
},
|
|
287
287
|
{
|
|
288
288
|
path: '/ai/ai-jobs-and-activity',
|
|
289
289
|
title: 'AI jobs and activity',
|
|
290
290
|
heading: 'Cancel a job',
|
|
291
291
|
anchor: '#cancel-a-job',
|
|
292
|
-
text: 'You can stop a job at any point before it finishes. Cancel is on:\n- the job\'s own page, such as Building your site;\n- each row of a site\'s AI jobs page, from the row\'s ⋮ menu (Cancel job);\n- each running job in the AI jobs list in Assist, which the AI chip in the top bar opens.\nEach asks first, in a Cancel this AI job? window. Choose Cancel job to stop, or Keep building to let it carry on. Cancel needs the Generate with AI permission on the site.\nWhat happens when you cancel:\n- Nothing more runs. If a step is in progress, it stops, or finishes if it is about to, and the job shows Stopping until it has. Nothing after it starts.\n- What it built stays, as drafts. Pages, layouts and forms it already made are kept as unpublished drafts for you to open, edit or delete. A canceled job never publishes anything, so your live site is unchanged.\n- You pay only for what ran. Credits held for the steps that did not run are released. The steps that finished stay charged, and the job says how much, for example This job used 42 credits before it stopped. A job you cancel is not counted as a failure, so it is not given back and you are not sent a "job stopped" notice.\n- It is recorded. Canceled an AI generation is added to the site\'s activity, with who canceled it.\nA canceled job shows Canceled in every list. A job that is already Done or Failed cannot be canceled; its Cancel is turned off and says why.\nCancel a new site {#cancel-a-new-site}\nIf you cancel a site you started with AI, the Building your site page says You canceled your site and offers:\n- Start again, which reopens the questions with your answers filled in, for a fresh job;\n- Use the starter site instead, which gives the site the starter home page. It is offered only while the job had not built anything
|
|
292
|
+
text: 'You can stop a job at any point before it finishes. Cancel is on:\n- the job\'s own page, such as Building your site;\n- each row of a site\'s AI jobs page, from the row\'s ⋮ menu (Cancel job);\n- each running job in the AI jobs list in Assist on a workspace page, which the AI chip in the top bar opens.\nEach asks first, in a Cancel this AI job? window. Choose Cancel job to stop, or Keep building to let it carry on. Cancel needs the Generate with AI permission on the site.\nWhat happens when you cancel:\n- Nothing more runs. If a step is in progress, it stops, or finishes if it is about to, and the job shows Stopping until it has. Nothing after it starts.\n- What it built stays, as drafts. Pages, layouts and forms it already made are kept as unpublished drafts for you to open, edit or delete. A canceled job never publishes anything, so your live site is unchanged.\n- You pay only for what ran. Credits held for the steps that did not run are released. The steps that finished stay charged, and the job says how much, for example This job used 42 credits before it stopped. A job you cancel is not counted as a failure, so it is not given back and you are not sent a "job stopped" notice.\n- It is recorded. Canceled an AI generation is added to the site\'s activity, with who canceled it.\nA canceled job shows Canceled in every list. A job that is already Done or Failed cannot be canceled; its Cancel is turned off and says why.\nCancel a new site {#cancel-a-new-site}\nIf you cancel a site you started with AI, the Building your site page says You canceled your site and offers:\n- Start again, which reopens the questions with your answers filled in, for a fresh job;\n- Use the starter site instead, which gives the site the starter home page. It is offered only while the job had not built anything '
|
|
293
293
|
},
|
|
294
294
|
{
|
|
295
295
|
path: '/ai/ai-jobs-and-activity',
|
|
@@ -380,28 +380,35 @@ export const DOCS_SECTION_INDEX = [
|
|
|
380
380
|
title: 'Build from Assist chat',
|
|
381
381
|
heading: 'Ask or build',
|
|
382
382
|
anchor: '#ask-or-build',
|
|
383
|
-
text: 'Assist decides from your message whether you are asking or asking for something to be made:\n- A question, such as how do I connect a domain?, gets an answer from the docs.\n- A change to the page you have open in the Besigner gets a proposed edit.\n- Something to make gets a plan card in the chat.\nIt builds only on a site, and only what your plan includes and the site has turned on. When you ask for something it cannot make from the chat, it says so plainly and plans the rest.'
|
|
383
|
+
text: 'Assist decides from your message whether you are asking or asking for something to be made:\n- A question, such as how do I connect a domain?, gets an answer from the docs.\n- A change to the page you have open in the Besigner gets a proposed edit.\n- A change to a page the site already has, asked anywhere else on the site, is made as a draft of that page, with no plan to confirm. See Change a page.\n- Something to make gets a plan card in the chat.\nEach site has its own conversation. What you asked on one site is never part of a request on another, and the workspace\'s own pages, such as Billing, have one of their own.\nIt builds only on a site, and only what your plan includes and the site has turned on. When you ask for something it cannot make from the chat, it says so plainly and plans the rest.'
|
|
384
|
+
},
|
|
385
|
+
{
|
|
386
|
+
path: '/ai/assist-builds',
|
|
387
|
+
title: 'Build from Assist chat',
|
|
388
|
+
heading: 'Change a page',
|
|
389
|
+
anchor: '#change-a-page',
|
|
390
|
+
text: 'Ask for a change to a page the site already has, such as make the image at the top of the home page fill the background, and Assist makes it on that page:\n1. The card says Making the change as a draft of Home… while it works.\n2. The change is saved into the page\'s draft, the same draft the Besigner keeps for you when you work on a page. Your published page stays as it is: visitors see no change until you publish.\n3. The card then says where the change is, with Open in the Besigner. Choose Open draft there to see the change, then publish it when you are happy with it. To leave it, choose Discard instead.\nThere is no plan to confirm, and nothing is added to the page that you did not ask for. If you already had a draft of the page, the change is made on it, so your own work is kept. Ask for another change to the same page and it is made on the same draft, so the draft holds every change you asked for. If a change could not be made, the card says why, with Try again.\nThis works on every plan. To keep the change apart as a new version instead, say so, such as make the hero image fill the background, as a new version. A new version needs version history, which comes with a Pro plan; without it, the change goes into the draft and the card says so.\nOne message changes one page. For changes to several pages, ask for the next one when the first is ready.'
|
|
384
391
|
},
|
|
385
392
|
{
|
|
386
393
|
path: '/ai/assist-builds',
|
|
387
394
|
title: 'Build from Assist chat',
|
|
388
395
|
heading: 'What one request can build',
|
|
389
396
|
anchor: '#what-it-can-build',
|
|
390
|
-
text: 'One message can ask for any mix of:\n- pages: home, about, services, contact, pricing, a landing page;\n- a header and footer shared by the pages;\n- a form: a contact form, a quote request, a sign-up form;\n- a reusable component: a card or block placed on several pages;\n- an email design, such as a welcome, a reply or an announcement, and an email campaign, drafted and left unsent;\n- a page template for blog posts, products or authors;\n- an automation: when a form is sent, do something;\n- a site function that works out a value, such as a price or a quote, and site variables, such as a phone number kept in one place;\n- products to sell, with a description, tags and options;\n- a booking service visitors can book online, with its length, hours and price;\n- events on the site\'s calendar, each with its date and time, place, description and a cover photo, published so the Event List on your pages shows them. They need the Event Calendar add-on. See Events Calendar;\n- an announcement bar or a popup;\n- an A/B test of a page or of an email\'s subject line;\n- a funnel that counts visits from one step to the next;\n- CRM setup: a deal pipeline with its stages, custom fields on contacts, companies, deals or leads, and new values for a picklist such as lead status or source. These are saved straight to your CRM, as they are when you set them up yourself;\n- a change to a page or layout the site already has,
|
|
397
|
+
text: 'One message can ask for any mix of:\n- pages: home, about, services, contact, pricing, a landing page;\n- a header and footer shared by the pages;\n- a form: a contact form, a quote request, a sign-up form;\n- a reusable component: a card or block placed on several pages;\n- an email design, such as a welcome, a reply or an announcement, and an email campaign, drafted and left unsent;\n- a page template for blog posts, products or authors;\n- an automation: when a form is sent, do something;\n- a site function that works out a value, such as a price or a quote, and site variables, such as a phone number kept in one place;\n- products to sell, with a description, tags and options;\n- a booking service visitors can book online, with its length, hours and price;\n- events on the site\'s calendar, each with its date and time, place, description and a cover photo, published so the Event List on your pages shows them. They need the Event Calendar add-on. See Events Calendar;\n- an announcement bar or a popup;\n- an A/B test of a page or of an email\'s subject line;\n- a funnel that counts visits from one step to the next;\n- CRM setup: a deal pipeline with its stages, custom fields on contacts, companies, deals or leads, and new values for a picklist such as lead status or source. These are saved straight to your CRM, as they are when you set them up yourself;\n- a change to a page or layout the site already has, alongside the rest of a request, saved into its draft, which visitors do not see until you publish it. A change to one page on its own needs no plan: see Change a page;\n- redirects: send an old address to a page you have, change where a redirect goes, or stop one, such as redirect /old-menu to /menu. See Redirects;\n- a change to the site\'s settings: its name, search title and descript'
|
|
391
398
|
},
|
|
392
399
|
{
|
|
393
400
|
path: '/ai/assist-builds',
|
|
394
401
|
title: 'Build from Assist chat',
|
|
395
402
|
heading: 'The plan card',
|
|
396
403
|
anchor: '#the-plan-card',
|
|
397
|
-
text: 'The card shows Planning what to build on this site… while the plan is made, then the Proposed plan, one line per part:\n- Reuses something the site already has, and what for;\n- Creates something new, and why nothing you have will do;\n- Builds the page with its title, address, layout and sections;\n- any video player a page will carry, and what loading it costs your visitors;\n- Leaves out anything you asked for that this build can\'t make, such as a page whose purpose is a feature your site doesn\'t have, and why. No page in the plan sends visitors to it.\nUnder the lines is the Estimated cost, such as About 106 credits (up to 650): about what builds like it cost, and the most it can cost. What the build costs is what its steps spend. On the Free plan the card also says how many free credits you have left this month. If you asked for the new pages to go live, a Publish the new pages when they are built box is there too, unticked until you tick it.\nIf the build will likely use more than your credits left, the card says so instead of offering Confirm plan, and gives you three choices: Build what fits (it builds what your credits cover and pauses, then Resume carries on), Build the home page first (only the home page and what it needs), or Upgrade. See Before a job starts.\nNothing is built while the card waits. The plan follows the building rules, and a plan that breaks them, or asks for more than your plan includes, is stopped before you are asked to confirm it.'
|
|
404
|
+
text: 'The card shows Planning what to build on this site… while the plan is made, then the Proposed plan, one line per part:\n- Reuses something the site already has, and what for;\n- Creates something new, and why nothing you have will do;\n- Builds the page with its title, address, layout and sections;\n- any video player a page will carry, and what loading it costs your visitors;\n- Leaves out anything you asked for that this build can\'t make, such as a page whose purpose is a feature your site doesn\'t have, and why. No page in the plan sends visitors to it.\nUnder the lines is the Estimated cost, such as About 106 credits (up to 650): about what builds like it cost, and the most it can cost. What the build costs is what its steps spend. On the Free plan the card also says how many free credits you have left this month. If you asked for the new pages to go live, a Publish the new pages when they are built box is there too, unticked until you tick it.\nIf the build will likely use more than your credits left, the card says so instead of offering Confirm plan, and gives you three choices: Build what fits (it builds what your credits cover and pauses, then Resume carries on), Build the home page first (only the home page and what it needs), or Upgrade. See Before a job starts.\nTo change the plan before you confirm it, say what to change in the chat, such as leave out the services grid. Assist plans again with your change, and the new plan replaces the one waiting for you: that one is canceled and says Replaced by the updated plan below, so there is only ever one plan to confirm.\nNothing is built while the card waits. The plan follows the building rules, and a plan that breaks them, or asks for more than your plan includes, is stopped before you are asked to confirm it.'
|
|
398
405
|
},
|
|
399
406
|
{
|
|
400
407
|
path: '/ai/assist-builds',
|
|
401
408
|
title: 'Build from Assist chat',
|
|
402
409
|
heading: 'Confirm the plan',
|
|
403
410
|
anchor: '#confirm-the-plan',
|
|
404
|
-
text: 'Confirm plan builds it. The card then shows Building each part in turn and a row per part, such as Page: Pricing — building, that reads built, building, waiting, failed or not built. You can close the chat; the job keeps going, and Open in AI jobs
|
|
411
|
+
text: 'Confirm plan builds it. The card then shows Building each part in turn and a row per part, such as Page: Pricing — building, that reads built, building, waiting, failed or not built. You can close the chat; the job keeps going, and Open in AI jobs opens the job on the site\'s AI jobs page.\nConfirming checks your permissions and credits again, so a plan confirmed after your credits ran out waits instead of building.'
|
|
405
412
|
},
|
|
406
413
|
{
|
|
407
414
|
path: '/ai/assist-builds',
|
|
@@ -1017,7 +1024,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
1017
1024
|
title: 'How Aglyn AI builds',
|
|
1018
1025
|
heading: 'The plan comes first',
|
|
1019
1026
|
anchor: '#the-plan-comes-first',
|
|
1020
|
-
text: 'Before it generates anything, a build job proposes a plan:\n- what it will reuse from your site: components, layouts, templates, forms, datasets and collections;\n- what it will create, and why nothing you already have will do;\n- the pages it will build, each with its layout, address, search title and sections;\n- any YouTube or Vimeo player your brief asks for, the page or component it goes on, and what it costs: a player loads its host\'s own code when a visitor reaches it, whether or not they press play. A brief that asks for no video gets no player.\nA plan only proposes what your workspace can create: what your plan includes, and what your site still has room for. A plan the job could not build is stopped before you are asked to confirm it, with the reason. What a page\'s plan creates, such as its layout, a card that repeats or its form, is built first when you confirm, in the same job. If another build on the same site used the last form your plan includes after you confirmed, the page places the form that build just made instead, and the job says so. When no such form will do, the job stops, and you are not charged for what it could not build. Starting a page while another is being built on the same site says A page is already being built: wait for it, or start another anyway.\nThe job then waits for you. The window you started it from stays with it: it shows the job planning, then the plan itself, with Confirm plan to build it and Cancel job to stop. Nothing is generated until you confirm.'
|
|
1027
|
+
text: 'Before it generates anything, a build job proposes a plan:\n- what it will reuse from your site: components, layouts, templates, forms, datasets and collections;\n- what it will create, and why nothing you already have will do;\n- the pages it will build, each with its layout, address, search title and sections;\n- any YouTube or Vimeo player your brief asks for, the page or component it goes on, and what it costs: a player loads its host\'s own code when a visitor reaches it, whether or not they press play. A brief that asks for no video gets no player.\nA plan only proposes what your workspace can create: what your plan includes, and what your site still has room for. A plan the job could not build is stopped before you are asked to confirm it, with the reason. What a page\'s plan creates, such as its layout, a card that repeats or its form, is built first when you confirm, in the same job. If another build on the same site used the last form your plan includes after you confirmed, the page places the form that build just made instead, and the job says so. When no such form will do, the job stops, and you are not charged for what it could not build. Starting a page while another is being built on the same site says A page is already being built: wait for it, or start another anyway. A plan still waiting for you to confirm it is not being built, so it never shows that message.\nThe job then waits for you. The window you started it from stays with it: it shows the job planning, then the plan itself, with Confirm plan to build it and Cancel job to stop. Nothing is generated until you confirm.'
|
|
1021
1028
|
},
|
|
1022
1029
|
{
|
|
1023
1030
|
path: '/ai/how-aglyn-ai-builds',
|
|
@@ -2277,7 +2284,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
2277
2284
|
title: 'The Besigner',
|
|
2278
2285
|
heading: 'Preview vs. canvas',
|
|
2279
2286
|
anchor: '#preview-vs-canvas',
|
|
2280
|
-
text: 'The canvas is an editing surface: hidden panels expand when you select them, so you can style what you can\'t otherwise reach, and nothing responds to hover the way a visitor would experience it.\nPreview (in the toolbar) renders the same draft the way the published site will: author-hidden panels start closed, and hover and click interactions actually run — so a mega menu, dropdown, or popup behaves exactly as it will live.\nTwo deliberate differences from the real site:\n- Links don\'t navigate. You stay on the page you\'re previewing.\n- Server-side steps don\'t fire — no analytics events, webhooks, or automations. A preview never writes data or spends quota.\nUse Preview to check interaction behavior before publishing, and the canvas to edit the parts a visitor would never see open.\nPlan availability Free. The Besigner is core to building; some components and actions it exposes are plan-gated (noted where relevant).'
|
|
2287
|
+
text: 'The canvas is an editing surface: hidden panels expand when you select them, so you can style what you can\'t otherwise reach, and nothing responds to hover the way a visitor would experience it.\nPreview (in the toolbar) renders the same draft the way the published site will: author-hidden panels start closed, and hover and click interactions actually run — so a mega menu, dropdown, or popup behaves exactly as it will live.\nTwo deliberate differences from the real site:\n- Links don\'t navigate. You stay on the page you\'re previewing.\n- Server-side steps don\'t fire — no analytics events, webhooks, or automations. A preview never writes data or spends quota.\nUse Preview to check interaction behavior before publishing, and the canvas to edit the parts a visitor would never see open.\nPublish from a preview {#publish-from-a-preview}\nA preview of a saved page version, such as the one an AI job opens, has a small bar in its corner. It says whether that version is live, and offers Open in Besigner and Publish. Publish asks first. On a live page it makes this version the one visitors see; on a page that isn\'t on your site yet, it publishes the page at its address with this version.\nPublish waits, with the reason shown, when your role on the site can\'t publish, when the page has no address yet (or a page above it isn\'t published), when the address is taken, or when the preview is showing changes from the Besigner that may not be saved. Open the page in the Besigner to sort any of these out.\nPlan availability Free. The Besigner is core to building; some components and actions it exposes are plan-gated (noted where relevant).'
|
|
2281
2288
|
},
|
|
2282
2289
|
{
|
|
2283
2290
|
path: '/building-sites/besigner/overview',
|
|
@@ -2375,7 +2382,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
2375
2382
|
title: 'Repeat over data',
|
|
2376
2383
|
heading: 'See the copies while you design',
|
|
2377
2384
|
anchor: '#see-the-copies-while-you-design',
|
|
2378
|
-
text: 'The canvas draws the copies from your real records, the same ones the published page will render, in the same order. A repeat badge in the top-right corner of the repeating element names what it repeats over and how many records it found — for example ⟳ Repeats Team · 3 records.\nWhen no record matches — the dataset is empty, or the filter rules every record out — the badge turns amber and says no records match · not shown on your site. The canvas still shows your design so you can keep editing it, with each {{item.}} drawn as a named chip, but the published page renders no copies at all rather than a card full of {{item.name}} placeholders.\nHover a badge to read what it means and how to fix it. Click it and the repeating element is selected, with Repeat over dataset opened in the Attributes panel.\nThe first copy is the element you edit. Change a color, retype a heading, drag something in — every copy changes with it, because there is only ever one design. The copies beside it are pictures: hovering one says so
|
|
2385
|
+
text: 'The canvas draws the copies from your real records, the same ones the published page will render, in the same order. A repeat badge in the top-right corner of the repeating element names what it repeats over and how many records it found — for example ⟳ Repeats Team · 3 records.\nWhen no record matches — the dataset is empty, or the filter rules every record out — the badge turns amber and says no records match · not shown on your site. The canvas still shows your design so you can keep editing it, with each {{item.}} drawn as a named chip, but the published page renders no copies at all rather than a card full of {{item.name}} placeholders.\nHover a badge to read what it means and how to fix it. Click it and the repeating element is selected, with Repeat over dataset opened in the Attributes panel.\nThe first copy is the element you edit. Change a color, retype a heading, drag something in — every copy changes with it, because there is only ever one design. The copies beside it are pictures: hovering one says so. Click any part of a copy — a heading in the third card, say — and the outline goes round exactly what you clicked, while the panels edit the element it copies, so the change shows in every copy at once. To type new text in place, double-click it in the first copy.'
|
|
2379
2386
|
},
|
|
2380
2387
|
{
|
|
2381
2388
|
path: '/building-sites/besigner/repeat',
|
|
@@ -6729,7 +6736,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
6729
6736
|
title: 'Activities & the timeline',
|
|
6730
6737
|
heading: 'Logging an activity',
|
|
6731
6738
|
anchor: '#logging-an-activity',
|
|
6732
|
-
text: 'Open the record — a contact\'s page under CRM › Contacts, a company\'s under Companies, a deal\'s under Deals, or a lead\'s under Leads — and choose Log activity in the header of the Timeline or Activity card. The activity is filed against that record; there is no picker, because what you are looking at is what the activity is about.\nLogging an activity is part of the CRM, included from Starter. On Free the CRM is shown locked, so there is no record page to log from.\n| Field | What it is |\n| Kind | Call, Email, Meeting, Note or Other. |\n| Direction | For a call: Outbound (your team placed it), Inbound (they called you) or Internal (a call between teammates about the record) — Salesforce\'s Call Type. For an email: Outbound or Inbound. Outbound to start; Not said leaves it off. |\n| When | When it happened, which is not always when you are logging it. Defaults to now. |\n| What happened | The body of the entry. |\n| Outcome | For a call or a meeting: how it ended — "left a voicemail", "agreed to a trial". |\n| Minutes | For a call or a meeting: how long it took. |\nA call
|
|
6739
|
+
text: 'Open the record — a contact\'s page under CRM › Contacts, a company\'s under Companies, a deal\'s under Deals, or a lead\'s under Leads — and choose Log activity in the header of the Timeline or Activity card. The activity is filed against that record; there is no picker, because what you are looking at is what the activity is about.\nLogging an activity is part of the CRM, included from Starter. On Free the CRM is shown locked, so there is no record page to log from.\n| Field | What it is |\n| Kind | Call, Email, Text message, WhatsApp, Facebook Messenger, Instagram, LinkedIn, Meeting, Note or Other — how the conversation happened, so a message on any channel is logged as itself rather than as Other. |\n| Direction | For a call: Outbound (your team placed it), Inbound (they called you) or Internal (a call between teammates about the record) — Salesforce\'s Call Type. For an email or a message (text, WhatsApp, Messenger, Instagram, LinkedIn): Outbound (you sent it) or Inbound (they wrote to you). Outbound to start; Not said leaves it off. |\n| When | When it happened, which is not always when you are logging it. Defaults to now. |\n| What happened | The body of the entry. |\n| Outcome | For a call or a meeting: how it ended — "left a voicemail", "agreed to a trial". |\n| Minutes | For a call or a meeting: how long it took. |\nA call, an email or a message with a direction reads as it in its chip — Inbound call, Outbound email, Internal call, Outbound WhatsApp message. The Log a CRM activity automation step and POST /v1/activities take the same direction (direction), and only on a call, an email or a message.\nEach entry shows who logged it and how long ago. The author can edit or delete their own entries; an org-wide member can edit or delete anyone\'s. A colleague with access to only '
|
|
6733
6740
|
},
|
|
6734
6741
|
{
|
|
6735
6742
|
path: '/content-and-data/crm/activities',
|
|
@@ -7184,7 +7191,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
7184
7191
|
title: 'Deals pipeline',
|
|
7185
7192
|
heading: 'The board and the table',
|
|
7186
7193
|
anchor: '#the-board-and-the-table',
|
|
7187
|
-
text: 'The section opens as a board of the chosen pipeline: one column per open stage, with Won and Lost folded away at the end until you expand them; a board wider than the window scrolls
|
|
7194
|
+
text: 'The section opens as a board of the chosen pipeline: one column per open stage, with Won and Lost folded away at the end until you expand them. A stage with no deals in it folds to a narrow labeled strip, so the stages holding work get the room; you can still drag a card onto it. When the board is still wider than the window, arrows at either end page it sideways, and it scrolls like any other row. Each card shows the deal\'s title, amount, the contact and company it is with, its owner, and how many days it has sat in its current stage. Drag a card between columns to move it, or use the card\'s menu to move it, mark it won, or mark it lost from the keyboard.\nAbove the board, three figures summarize what is open: the open count, the pipeline value (every open deal\'s amount, per currency) and the weighted value (each amount multiplied by its probability — the deal\'s own when it has one, otherwise its stage\'s).\nSwitch to the table for a paged list with the title, stage, amount, owner, expected close date, status and next activity of every deal in the chosen pipeline, including the closed ones, most recently changed first. Type and Lead source are optional columns: turn them on from the column menu. The table\'s Filters panel narrows it by Status (open, won or lost — one, or any of them), by Type and by Lead source (one value, any of several, or No type / No lead source), and Next activity › is empty keeps only the deals with no open task scheduled against them — the ones the reports page counts as stuck. Search finds a deal by any word of its title.\nEvery filter and the search are answered by the table\'s query, so they reach every deal in the pipeline, a page at a time, not only the page on screen, and filters on different columns add up. The search matches whole words from t'
|
|
7188
7195
|
},
|
|
7189
7196
|
{
|
|
7190
7197
|
path: '/content-and-data/crm/deals',
|
|
@@ -7226,7 +7233,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
7226
7233
|
title: 'Deals pipeline',
|
|
7227
7234
|
heading: 'A deal\'s page',
|
|
7228
7235
|
anchor: '#a-deals-page',
|
|
7229
|
-
text: 'A deal\'s page is where you work one deal: its stage, what it is worth, the people on it and what is owed on it, each on a card of its own. Opening a deal shows:\n- The header — the deal\'s title in the page heading and the trail, the pipeline and stage under its kind, its status, amount and owner as chips, Back to deals, Edit, and a menu (⋮) carrying Delete deal.\n- Stage —
|
|
7236
|
+
text: 'A deal\'s page is where you work one deal: its stage, what it is worth, the people on it and what is owed on it, each on a card of its own. Opening a deal shows:\n- The header — the deal\'s title in the page heading and the trail, the pipeline and stage under its kind, its status, amount and owner as chips, Back to deals, Edit, and a menu (⋮) carrying Delete deal.\n- Stage — the deal\'s path through the whole pipeline, the way Salesforce draws one: every open stage, so the stages still ahead are always in view, then a final Closed step. Choose an open stage to move there; choose Closed to mark the deal won or lost (the Won and Lost buttons do the same). On a closed deal the path stays, every stage ticked and the last step reading the pipeline\'s own name for the verdict, with the way to reopen it below. The line under an open deal\'s path says how long it has sat in its stage, its probability and its forecast category.\n- Properties — what the deal is worth and where it stands; see Deal properties.\n- Contact roles — every person on the deal, the part each plays, and the Primary; see Contact roles.\n- Products — the line items behind the amount, with the door to add one from the catalog or by hand.\n- Tasks and Activity — what is owed on this deal and what has happened on it.\nDeal properties {#deal-properties}\nThe Properties card lists what the deal is worth and where it stands; to change any of it, choose Edit in the page\'s header, which carries a control for each.\nIt shows the amount and its weighted value, the probability (the deal\'s own beside its stage\'s, 40% · from stage: 75%), the forecast category, the expected close, the type, lead source and next step, the owner, links to the contact and the company, the campaign, the notes, and one row per custom field defined on the De'
|
|
7230
7237
|
},
|
|
7231
7238
|
{
|
|
7232
7239
|
path: '/content-and-data/crm/deals',
|
|
@@ -7646,7 +7653,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
7646
7653
|
title: 'Reports',
|
|
7647
7654
|
heading: 'Activity by teammate',
|
|
7648
7655
|
anchor: '#activity-by-teammate',
|
|
7649
|
-
text: 'Who did what in the period, busiest first.\n- Activities logged — every call, email, meeting, note and other activity logged in the period, counted on the server, with the change against the previous period.\n- Tasks completed — tasks ticked off in the period, counted on the server.\n- Teammates active — how many people logged or completed something.\n- Who did what — one row per teammate: their calls, emails, meetings, notes and other activities, the total, and the tasks they completed. A task is credited to whoever completed it, or to its assignee when the completer was not recorded. Activities an automation logged, and tasks completed with nobody assigned, share one row called No teammate.\nTeammates are named from the workspace roster when it knows them, and otherwise by the name each activity was signed with, so a former member\'s work still reads under their name. The table is grouped from the period\'s 1,000 most recent activities and 1,000 most recently completed tasks and says so when the period held more; the tiles are always the server\'s count.'
|
|
7656
|
+
text: 'Who did what in the period, busiest first.\n- Activities logged — every call, email, message, meeting, note and other activity logged in the period, counted on the server, with the change against the previous period.\n- Tasks completed — tasks ticked off in the period, counted on the server.\n- Teammates active — how many people logged or completed something.\n- Who did what — one row per teammate: their calls, emails, meetings, notes and other activities, the total, and the tasks they completed. A task is credited to whoever completed it, or to its assignee when the completer was not recorded. Activities an automation logged, and tasks completed with nobody assigned, share one row called No teammate.\nTeammates are named from the workspace roster when it knows them, and otherwise by the name each activity was signed with, so a former member\'s work still reads under their name. The table is grouped from the period\'s 1,000 most recent activities and 1,000 most recently completed tasks and says so when the period held more; the tiles are always the server\'s count.'
|
|
7650
7657
|
},
|
|
7651
7658
|
{
|
|
7652
7659
|
path: '/content-and-data/crm/reports',
|
|
@@ -10320,7 +10327,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10320
10327
|
title: 'Aglyn Assist',
|
|
10321
10328
|
heading: 'What it can do',
|
|
10322
10329
|
anchor: '#what-it-can-do',
|
|
10323
|
-
text: '- Answer how-to questions about building sites, publishing, domains, commerce, bookings, workflows, datasets, team roles, and billing.\n- Link you to the source — under each written answer is a Sources list naming the documentation sections it drew on, each one a link straight to that section. See Where an answer came from.\n- Guide you on the page you\'re on (Starter and up) — the assistant knows which console page you\'re viewing and answers about that page, rather than giving you a general answer you then have to translate.\n- Offer to take you to the right page (Starter and up) — when what you asked for starts somewhere else, it can show a card that opens that page for you. See Offers to open a page.\n- Propose edits in the Besigner (with AI generation on your plan) — ask for a change to the page, component or layout you have open, and it shows exactly what would change before anything does. See Edits in the Besigner.\n- Answer in your language — ask in any language and it answers in that language. It looks your question up in this documentation, which is in English, so its Sources are English pages.\n- Know where your AI jobs stand — it can see the workspace\'s open AI jobs, so it can tell you that a plan is ready and that nothing is built until you choose Confirm plan. It also knows which plan your workspace is on.\nThe chat takes text only: you can\'t attach a file, an image or a screenshot to
|
|
10330
|
+
text: '- Answer how-to questions about building sites, publishing, domains, commerce, bookings, workflows, datasets, team roles, and billing.\n- Link you to the source — under each written answer is a Sources list naming the documentation sections it drew on, each one a link straight to that section. See Where an answer came from.\n- Guide you on the page you\'re on (Starter and up) — the assistant knows which console page you\'re viewing and answers about that page, rather than giving you a general answer you then have to translate.\n- Offer to take you to the right page (Starter and up) — when what you asked for starts somewhere else, it can show a card that opens that page for you. See Offers to open a page.\n- Propose edits in the Besigner (with AI generation on your plan) — ask for a change to the page, component or layout you have open, and it shows exactly what would change before anything does. See Edits in the Besigner.\n- Change a page as a draft (with AI generation) — ask for a change to one of the site\'s pages from anywhere on the site, and it saves the change into that page\'s draft, with Open in the Besigner to check it and publish it. See Change a page.\n- Keep one conversation per site — each site has its own conversation, so what you asked on one site never becomes part of a request on another.\n- Answer in your language — ask in any language and it answers in that language. It looks your question up in this documentation, which is in English, so its Sources are English pages.\n- Know where your AI jobs stand — it can see the workspace\'s open AI jobs, so it can tell you that a plan is ready and that nothing is built until you choose Confirm plan. It also knows which plan your workspace is on.\nThe chat takes text only: you can\'t attach a file, an image or a screenshot to '
|
|
10324
10331
|
},
|
|
10325
10332
|
{
|
|
10326
10333
|
path: '/getting-started/aglyn-assist',
|
|
@@ -10341,7 +10348,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10341
10348
|
title: 'Aglyn Assist',
|
|
10342
10349
|
heading: 'Offers to open a page',
|
|
10343
10350
|
anchor: '#offers-to-open-a-page',
|
|
10344
|
-
text: 'Sometimes the thing you asked about starts on a different page. When the assistant knows which one, it shows a small card offering to take you there — with the values to use, when it has worked them out from your question.\nThe card only opens the page. It never fills in a form for you, never saves anything, and never makes a change on your behalf. You land on the normal page, fill it in yourself, and press the button yourself — with all the usual permission checks in place. If you\'d rather stay where you are, choose No thanks and the card goes away.\nThis is deliberate. A card that only opens a page cannot change your site by misunderstanding you, because it has no way to. The
|
|
10351
|
+
text: 'Sometimes the thing you asked about starts on a different page. When the assistant knows which one, it shows a small card offering to take you there — with the values to use, when it has worked them out from your question.\nThe card only opens the page. It never fills in a form for you, never saves anything, and never makes a change on your behalf. You land on the normal page, fill it in yourself, and press the button yourself — with all the usual permission checks in place. If you\'d rather stay where you are, choose No thanks and the card goes away.\nThis is deliberate. A card that only opens a page cannot change your site by misunderstanding you, because it has no way to. The changes the assistant can make are the edits in the Besigner, each of which waits for you to apply it, the builds you confirm, and changes to a page saved as a draft that visitors don\'t see until you publish it.'
|
|
10345
10352
|
},
|
|
10346
10353
|
{
|
|
10347
10354
|
path: '/getting-started/aglyn-assist',
|