Member Junction
    Preparing search index...

    Compact "Routines" entry pinned at the very bottom of the conversations left sidebar: a single header row — mark, "Routines", the ACTIVE routine count, a "+" (straight into the New Routine editor) and a details chevron. No routine rows — the full command-center slide-in is one click away and owns all detail.

    Visibility gates (both must pass):

    1. ShowRoutines — host opt-out input bubbled from the top-level conversations workspace (default true).
    2. The current user must have Read permission on 'MJ: User Routines' (EntityInfo user-permission check) — hidden entirely otherwise.

    Hierarchy (View Summary)

    Implements

    • OnInit
    • OnDestroy
    Index

    Constructors

    Properties

    ActiveCount: number = 0

    Number of Active routines — the header badge.

    CanRead: boolean = false

    True when the current user may read routines (permission gate).

    openConversation: EventEmitter<string> = ...

    The user asked to open a routine's dedicated conversation (the hidden, Application-scoped thread its runs append to). Emits the conversation ID; the host selects it in chat — this component closes the slide-in first.

    openEntityRecord: EventEmitter<
        { compositeKey: CompositeKey; entityName: string },
    > = ...

    A run history row's linked execution record (Agent Run / Prompt Run / Action Log) was clicked. Same shape as the chat area's openEntityRecord — the host (Explorer wrapper or workspace) routes it to navigation; this package never navigates itself.

    Provider: IMetadataProvider | null

    If specified, this provider will be used for communication and for all metadata purposes. By default, if not provided, the Metadata and RunView classes are used for this and the default GraphQLDataProvider is used which is connected to the same back-end MJAPI instance as the Metadata and RunView classes. If you want to have this component connect to a different MJAPI back-end, create an instance of a ProviderBase sub-class like GraphQLDataProvider/etc, and configure it as appropriate to connect to the MJAPI back-end you want to use, and then pass it in here.

    SlideInNewRoutine: boolean = false

    Whether the slide-in opens straight on the New Routine editor.

    SlideInRoutineID: string | null = null

    Routine to open the slide-in on (history view).

    SlideInVisible: boolean = false

    Slide-in open state.

    TotalCount: number = 0

    Total routines of any status (for the header tooltip).

    "ɵdir": unknown
    "ɵfac": unknown

    Accessors

    • get ProviderToUse(): IMetadataProvider

      Returns either the default Metadata provider or the one specified in the Provider property, if it was specified

      Returns IMetadataProvider

    • get RunQueryToUse(): IRunQueryProvider

      Returns either the default RunQuery provider or the one specified in the Provider property, if it was specified

      Returns IRunQueryProvider

    • get RunReportToUse(): IRunReportProvider

      Returns either the default RunReport provider or the one specified in the Provider property, if it was specified

      Returns IRunReportProvider

    • get RunViewToUse(): IRunViewProvider

      Returns either the default RunView provider or the one specified in the Provider property, if it was specified

      Returns IRunViewProvider

    Methods